Re: info vs. man (was: Re: date for week)

On Tue, Jun 11, 2024 at 11:22:17PM +0700, Max Nikulin wrote: > On 11/06/2024 06:45, Greg Wooledge wrote: > > Should you ever feel a need to read the longer version of the > > documentation, it's in GNU info pages. So you would need to type > > the command "info coreutils date" to get to it. And t

info vs. man (was: Re: date for week)

On 11/06/2024 06:45, Greg Wooledge wrote: Should you ever feel a need to read the longer version of the documentation, it's in GNU info pages. So you would need to type the command "info coreutils date" to get to it. And then you'd need to figure out the user interface of the "info" program, wh

Re: date for week

thanks roberto. that's exactly what i am looking for. $ date +%a

Re: date for week

On Tue, Jun 11, 2024 at 07:19:42AM +0800, Jeff Peng wrote: > While I expect the output should be: > > $ date +%such_a_option > Tuesday > > or > $ date +%such_a_option > Tue > > does date command has this option? You can run the command "man date" to read the short version of the documentation.

Re: date for week

All the format codes are documented in the man page for date. in particular: +%a gives a short form, such as Mon +%A gives full name, e.g. Monday +%^a and +%^A as above, but all capital letters. - Original Message - From: "Jeff Peng" To: "debian-user" > While I expect the output shou

Re: date for week

On Tue, Jun 11, 2024 at 07:19:42AM +0800, Jeff Peng wrote: > Hello, > > I run the folllowing command, > > $ date +%w > 2 > > > While I expect the output should be: > > $ date +%such_a_option > Tuesday > > or > $ date +%such_a_option > Tue > > does date command has this option? > > Thanks. >

Re: Date time problem bookworm, fvwm....

On Sun, Oct 22, 2023 at 01:51:41PM +0200, Thomas Schmitt wrote: [...] > Originally it did only put out text in an xterm, but then i shamelessly > exploited code from the exploitation chain xpppload <- xisdnload <- xload > to give it a histogram in ain additional separate window. Now this one bea

Re: Date time problem bookworm, fvwm....

On Sun, Oct 22, 2023 at 07:50:54AM -0400, The Wanderer wrote: > On 2023-10-22 at 07:24, to...@tuxteam.de wrote: > > > I better not tell. My clock is a... shell script in a tiny Xterm > > which also shows my battery status. > > Ooo, that sounds interesting. I don't currently have a laptop, so the

Re: Date time problem bookworm, fvwm....

On 2023-10-22 at 07:24, to...@tuxteam.de wrote: > I better not tell. My clock is a... shell script in a tiny Xterm > which also shows my battery status. Ooo, that sounds interesting. I don't currently have a laptop, so the battery-status part wouldn't currently apply, but this sounds like somethi

Re: Date time problem bookworm, fvwm....

Hi, to...@tuxteam.de wrote: > My clock is a... shell script in a tiny Xterm which > also shows my battery status. My digital clock with date display is a C program which mainly watches the network traffic. It even has an own date format ("A0" = 2000, now is "C3") which has an odd history beginnin

Re: Date time problem bookworm, fvwm....

On Sun, Oct 22, 2023 at 11:16:25AM +0200, Thomas Schmitt wrote: > Hi, > > Charlie wrote: > > I removed the clock from the > > FVWM task bar and Gkrellm now dis[pays the right time. So a fix > > of sorts with which I can live. > > Congrats. :)) > > > > being a bit long in > > the tooth to start

Re: Date time problem bookworm, fvwm....

Hi, Charlie wrote: > I removed the clock from the > FVWM task bar and Gkrellm now dis[pays the right time. So a fix > of sorts with which I can live. Congrats. :)) > being a bit long in > the tooth to start relearning another window manager. I'm using fvwm since the last century. It's configur

Re: Date time problem bookworm, fvwm....

On Sun, 22 Oct 2023 10:13:59 +0200 "Thomas Schmitt" wrote: > Hi, > > Charlie wrote: > > The date on that system is one day in advance and one hour late. Not > > terrible, > > However after a short period 100% of one of the CPU cores is used, > > noisy running, and top -c shows this as the user:

Re: Date time problem bookworm, fvwm....

Hi, Charlie wrote: > The date on that system is one day in advance and one hour late. Not > terrible, > However after a short period 100% of one of the CPU cores is used, > noisy running, and top -c shows this as the user: > /usr/libexe/fvwm2/2.7.0/FvwmScript 17 4 none 0 8 FvwmScript DateTime Loo

Re: date & X copy/paste broke on upgrading to Debian 11

On Sun, Feb 06, 2022 at 06:54:26PM +, Brian wrote: It does. Installation of chrony or ntp removeds the traditional systemd-timesyncd package. I'm somewhat amused by the characterization of systemd-timesyncd as "traditional" over ntpd, a program which has existed since the late 80s.

Re: date & X copy/paste broke on upgrading to Debian 11

On Sun, Feb 06, 2022 at 08:03:55PM -0600, David Wright wrote: > Technically, I think you get bracketed paste through anything that > uses readline (the animal that reads ~/.inputrc). Yes. Potentailly, at least. > As a workaround, do the CUA keys work? That is, cutting with ^X, > copying with ^C

Re: date & X copy/paste broke on upgrading to Debian 11

On Sun 06 Feb 2022 at 18:03:42 (-0500), Greg Wooledge wrote: > On Sun, Feb 06, 2022 at 11:58:52PM +0100, José Luis González wrote: > > On Sun, 6 Feb 2022 15:59:34 -0500 Greg Wooledge wrote: > > > On Sun, Feb 06, 2022 at 09:55:02PM +0100, José Luis González wrote: > > > > > > > > Does anybody know

Re: date & X copy/paste broke on upgrading to Debian 11

On Sun, Feb 06, 2022 at 11:58:52PM +0100, José Luis González wrote: > On Sun, 6 Feb 2022 15:59:34 -0500 > Greg Wooledge wrote: > > > On Sun, Feb 06, 2022 at 09:55:02PM +0100, José Luis González wrote: > > > Thanks everybody for your input. > > > > > > Does anybody know why the X copy/paste issue

Re: date & X copy/paste broke on upgrading to Debian 11

On Sun, 6 Feb 2022 15:59:34 -0500 Greg Wooledge wrote: > On Sun, Feb 06, 2022 at 09:55:02PM +0100, José Luis González wrote: > > Thanks everybody for your input. > > > > Does anybody know why the X copy/paste issue is happening? So far I > > have only got help with time. > > https://lists.debia

Re: date & X copy/paste broke on upgrading to Debian 11

On Sun, Feb 06, 2022 at 09:55:02PM +0100, José Luis González wrote: > Thanks everybody for your input. > > Does anybody know why the X copy/paste issue is happening? So far I > have only got help with time. https://lists.debian.org/debian-user/2022/02/msg00144.html https://lists.debian.org/debia

Re: date & X copy/paste broke on upgrading to Debian 11

On Sun, 6 Feb 2022 09:17:35 -0500 Greg Wooledge wrote: > On Sun, Feb 06, 2022 at 11:25:36AM +0100, Thomas Schmitt wrote: > > Hi, > > > > José Luis González wrote: > > > 2. Copy and paste in X don't work anymore by selecting and clicking on > > > mouse button 2. > > > > "bracketed paste", maybe

Re: date & X copy/paste broke on upgrading to Debian 11

Thanks everybody for your input. Does anybody know why the X copy/paste issue is happening? So far I have only got help with time. On Sun, 6 Feb 2022 18:54:26 + Brian wrote: > On Sun 06 Feb 2022 at 12:09:39 -0500, Greg Wooledge wrote: > > > On Sun, Feb 06, 2022 at 10:42:31AM -0600, David

Re: date & X copy/paste broke on upgrading to Debian 11

On Sun, 6 Feb 2022 11:20:37 + "Andrew M.A. Cater" wrote: > On Sun, Feb 06, 2022 at 11:58:08AM +0100, José Luis González wrote: > > Hi, > > > > Upon upgrading to Debian 11 several things broke. > > > > The two that come to my attention now are: > > > > 1. System time is one hour more than i

Re: date & X copy/paste broke on upgrading to Debian 11

On Sun 06 Feb 2022 at 12:09:39 -0500, Greg Wooledge wrote: > On Sun, Feb 06, 2022 at 10:42:31AM -0600, David Wright wrote: > > That said, I notice you have ntp installed. Does that mean that > > you're keeping your time synchronised with ntp and, if so, what > > do you do about systemd-timesyncd,

Re: date & X copy/paste broke on upgrading to Debian 11

On Sun, Feb 06, 2022 at 10:42:31AM -0600, David Wright wrote: > That said, I notice you have ntp installed. Does that mean that > you're keeping your time synchronised with ntp and, if so, what > do you do about systemd-timesyncd, which I understand is enabled > by default since several Debian vers

Re: date & X copy/paste broke on upgrading to Debian 11

On Sun 06 Feb 2022 at 09:44:54 -0700, Charles Curley wrote: > On Sun, 6 Feb 2022 09:12:01 -0500 > Greg Wooledge wrote: > > > My first question for José is: what does the date command *actually* > > say? (Follow-ups: What time zone are you in? How did you configure > > the time zone? Are you r

Re: date & X copy/paste broke on upgrading to Debian 11

On Sun, 6 Feb 2022 09:12:01 -0500 Greg Wooledge wrote: > My first question for José is: what does the date command *actually* > say? (Follow-ups: What time zone are you in? How did you configure > the time zone? Are you running an NTP daemon? If so, which one, and > what does "ntpq -p" report

Re: date & X copy/paste broke on upgrading to Debian 11

On Sun 06 Feb 2022 at 09:12:01 (-0500), Greg Wooledge wrote: > On Sun, Feb 06, 2022 at 02:00:21PM +0200, Teemu Likonen wrote: > > * 2022-02-06 11:58:08+0100, José Luis González wrote: > > > > > 1. System time is one hour more than it should. Timezone (as set by > > > tzdata) is correct. > > > > N

Re: date & X copy/paste broke on upgrading to Debian 11

On Sun, Feb 06, 2022 at 11:25:36AM +0100, Thomas Schmitt wrote: > Hi, > > José Luis González wrote: > > 2. Copy and paste in X don't work anymore by selecting and clicking on > > mouse button 2. > > "bracketed paste", maybe ? Depends on where he's pasting. Bracketed paste doesn't actually stop

Re: date & X copy/paste broke on upgrading to Debian 11

On Sun, Feb 06, 2022 at 02:00:21PM +0200, Teemu Likonen wrote: > * 2022-02-06 11:58:08+0100, José Luis González wrote: > > > 1. System time is one hour more than it should. Timezone (as set by > > tzdata) is correct. > > Nowadays "timedatectl" is used to configure time. Strongly disagree. I mea

Re: date & X copy/paste broke on upgrading to Debian 11

* 2022-02-06 11:58:08+0100, José Luis González wrote: > 1. System time is one hour more than it should. Timezone (as set by > tzdata) is correct. Nowadays "timedatectl" is used to configure time. Run the command without arguments first. Then see its manual page and perhaps use some of the followi

Re: date & X copy/paste broke on upgrading to Debian 11

On Sun, Feb 06, 2022 at 11:58:08AM +0100, José Luis González wrote: > Hi, > > Upon upgrading to Debian 11 several things broke. > > The two that come to my attention now are: > > 1. System time is one hour more than it should. Timezone (as set by > tzdata) is correct. > Hi System time: what

Re: date & X copy/paste broke on upgrading to Debian 11

Hi, José Luis González wrote: > 2. Copy and paste in X don't work anymore by selecting and clicking on > mouse button 2. "bracketed paste", maybe ? It was discussed on this list in the recent months. See https://lists.debian.org/cgi-bin/search?P=bracketed+paste&DEFAULTOP=or&B=Gdebian-user&SO

Re: Date format for Thunderbird 60.7 -- partial success in changing it

Thank you Greg for the clarification. I find your third link https://wiki.debian.org/DotFiles very worth reading. Regards, Jörg Greg Wooledge wrote on 05/06/2019 14:52: > On Wed, Jun 05, 2019 at 11:18:55AM +0200, Jörg-Volker Peetz wrote: >> As user of thunderbird you best set the environment vari

Re: Date format for Thunderbird 60.7 -- partial success in changing it

On Wed, Jun 05, 2019 at 11:18:55AM +0200, Jörg-Volker Peetz wrote: > As user of thunderbird you best set the environment variable LC_TIME in your > profile, e.g. via ~/.bash_profile . Check it with the command > > $ locale > > You have to log out (from desktop and from computer) before changes in

Re: Date format for Thunderbird 60.7 -- partial success in changing it

As user of thunderbird you best set the environment variable LC_TIME in your profile, e.g. via ~/.bash_profile . Check it with the command $ locale You have to log out (from desktop and from computer) before changes in .bash_profile get applied. Regards, Jörg.

Re: Date format for Thunderbird 60.7 -- partial success in changing it

On 2019-06-05, Ken Heard wrote: > > The latest version of Thunderbird for Debian Stretch, 70.7 which I now > use, still allows only the US date format, MM-DD-, but for me at > least expresses the time as HH:MM (24 hour clock). In a partially > successful attempt to change the date format I di

Re: date(1) in stretch and buster

On Wed 10 Apr 2019 at 13:26:39 (+0200), Vincent Lefevre wrote: > On 2019-04-09 13:28:40 -0500, David Wright wrote: > > On Tue 09 Apr 2019 at 15:38:43 (+0200), Vincent Lefevre wrote: > > > On 2019-04-08 18:26:23 +0300, Reco wrote: > > > > stretch$ TZ=UTC date > > > > Mon Apr 8 15:22:02 UTC 2019 > >

Re: date(1) in stretch and buster

On 2019-04-09 13:28:40 -0500, David Wright wrote: > On Tue 09 Apr 2019 at 15:38:43 (+0200), Vincent Lefevre wrote: > > On 2019-04-08 18:26:23 +0300, Reco wrote: > > > stretch$ TZ=UTC date > > > Mon Apr 8 15:22:02 UTC 2019 > > > buster$ TZ=UTC date > > > Mon 08 Apr 2019 03:22:04 PM UTC > > > > Thi

Re: date(1) in stretch and buster

On Tue 09 Apr 2019 at 20:07:37 (-), Curt wrote: > On 2019-04-09, Étienne Mollier wrote: > > > > The output may differ depending on you operating system level, > > given Reco's observations. Feel free to have à look at > > /usr/share/zoneinfo/, to have an idea of the available > > locations. >

Re: date(1) in stretch and buster

On 2019-04-09, Étienne Mollier wrote: > > The output may differ depending on you operating system level, > given Reco's observations. Feel free to have à look at > /usr/share/zoneinfo/, to have an idea of the available > locations. I took a look. I was confused to note the presence of the UCT z

Re: date(1) in stretch and buster

On Tue 09 Apr 2019 at 14:55:37 (-0400), Greg Wooledge wrote: > On Tue, Apr 09, 2019 at 01:28:40PM -0500, David Wright wrote: > > My question about the OP's issue is whether I'm going to have to > > change something to keep what I get in jessie and stretch, or is > > this just a temporary bug in bus

Re: date(1) in stretch and buster

On Tue 09 Apr 2019 at 20:46:53 (+0200), Étienne Mollier wrote: > On 4/9/19 8:39 PM, David Wright wrote: > > We avoided the problem when I went to sea by using the letter codes, > > Z(ulu), A(lpha), B(ravo) etc. because there are no civil timezones, > > daylight savings times or anything else. > >

Re: date(1) in stretch and buster

On Tuesday 09 April 2019 14:39:19 David Wright wrote: > On Tue 09 Apr 2019 at 14:03:08 (-0400), Gene Heskett wrote: > > On Tuesday 09 April 2019 09:38:43 Vincent Lefevre wrote: > > > On 2019-04-08 18:26:23 +0300, Reco wrote: > > > > stretch$ TZ=UTC date > > > > Mon Apr 8 15:22:02 UTC 2019 > > > >

Re: date(1) in stretch and buster

On Tue, Apr 09, 2019 at 03:11:27PM -0400, Gene Heskett wrote: The point I was trying to make Mike, is, if thats to be a std, its an extremely obtuse way of writing that std. Consequently I suspect it will be 100% ignored. And folks will continue to muddle along just fine. :) It reads fine to me

Re: date(1) in stretch and buster

On Tuesday 09 April 2019 14:28:18 Michael Stone wrote: > On Tue, Apr 09, 2019 at 02:03:08PM -0400, Gene Heskett wrote: > >On Tuesday 09 April 2019 09:38:43 Vincent Lefevre wrote: > >> On 2019-04-08 18:26:23 +0300, Reco wrote: > >> > stretch$ TZ=UTC date > >> > Mon Apr 8 15:22:02 UTC 2019 > >> > b

Re: date(1) in stretch and buster

On Tue, Apr 09, 2019 at 01:28:40PM -0500, David Wright wrote: > My question about the OP's issue is whether I'm going to have to > change something to keep what I get in jessie and stretch, or is > this just a temporary bug in buster. Or has the US format been > wrong all along? (As an expat, I'm u

Re: date(1) in stretch and buster

On 4/9/19 8:39 PM, David Wright wrote: > We avoided the problem when I went to sea by using the letter codes, > Z(ulu), A(lpha), B(ravo) etc. because there are no civil timezones, > daylight savings times or anything else. You mean, like this ? $ TZ=Zulu date Tue Apr 9 18:46:20

Re: date(1) in stretch and buster

On Tue 09 Apr 2019 at 14:03:08 (-0400), Gene Heskett wrote: > On Tuesday 09 April 2019 09:38:43 Vincent Lefevre wrote: > > On 2019-04-08 18:26:23 +0300, Reco wrote: > > > stretch$ TZ=UTC date > > > Mon Apr 8 15:22:02 UTC 2019 > > > buster$ TZ=UTC date > > > Mon 08 Apr 2019 03:22:04 PM UTC > > > >

Re: date(1) in stretch and buster

Gene Heskett, on 2019-04-09 : > On Tuesday 09 April 2019 09:38:43 Vincent Lefevre wrote: > > This is unrelated to your issue, but note that the correct TZ string > > for UTC is "UTC0", not "UTC". See > > > > http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.htm > > l > > Yikes. Can

Re: date(1) in stretch and buster

On Tue 09 Apr 2019 at 15:38:43 (+0200), Vincent Lefevre wrote: > On 2019-04-08 18:26:23 +0300, Reco wrote: > > stretch$ TZ=UTC date > > Mon Apr 8 15:22:02 UTC 2019 > > buster$ TZ=UTC date > > Mon 08 Apr 2019 03:22:04 PM UTC > > This is unrelated to your issue, but note that the correct TZ string

Re: date(1) in stretch and buster

On Tue, Apr 09, 2019 at 02:03:08PM -0400, Gene Heskett wrote: On Tuesday 09 April 2019 09:38:43 Vincent Lefevre wrote: On 2019-04-08 18:26:23 +0300, Reco wrote: > stretch$ TZ=UTC date > Mon Apr 8 15:22:02 UTC 2019 > buster$ TZ=UTC date > Mon 08 Apr 2019 03:22:04 PM UTC This is unrelated to yo

Re: date(1) in stretch and buster

On Tue, Apr 09, 2019 at 02:03:08PM -0400, Gene Heskett wrote: > Yikes. Can that be actually put into English? "Use date -u instead."

Re: date(1) in stretch and buster

On Tuesday 09 April 2019 09:38:43 Vincent Lefevre wrote: > On 2019-04-08 18:26:23 +0300, Reco wrote: > > stretch$ TZ=UTC date > > Mon Apr 8 15:22:02 UTC 2019 > > buster$ TZ=UTC date > > Mon 08 Apr 2019 03:22:04 PM UTC > > This is unrelated to your issue, but note that the correct TZ string > for

Re: date(1) in stretch and buster

On 2019-04-08 18:26:23 +0300, Reco wrote: > stretch$ TZ=UTC date > Mon Apr 8 15:22:02 UTC 2019 > buster$ TZ=UTC date > Mon 08 Apr 2019 03:22:04 PM UTC This is unrelated to your issue, but note that the correct TZ string for UTC is "UTC0", not "UTC". See http://pubs.opengroup.org/onlinepubs/969

Re: date(1) in stretch and buster

I managed to build a locale with a customized LC_TIME setting under buster. It's not documented in a straightforward manner anywhere I could find, so I'm going to spell it all out here. Step 1: Start with an existing locale definition. In my case, I am starting with Debian buster's en_US locale

Re: date(1) in stretch and buster

Cindy-Sue Causey, on 2019-04-08 : > Found this over at Tecmint: > > https://www.tecmint.com/set-system-locales-in-linux/ > > locale -k LC_TIME > > Very coo AND further implies *WHAT ELSE can that little puppy do*, but > my brain's already cognitively sundowning so am passing the baton on > for some

Re: date(1) in stretch and buster

Hi. On Mon, Apr 08, 2019 at 07:10:50PM +0200, Étienne Mollier wrote: > > My question is - can anyone suggest me appropriate LC_TIME setting that > > can show buster's date in stretch's format? > > $ LC_TIME=en_US.UTF-8 TZ=UTC date > Mon 08 Apr 2019 05:07:44 PM UTC > > $

Re: date(1) in stretch and buster

Hi, Cindy Sue Causey wrote: > I'd like mine to be in the '2009.04.08' format. $ date +'%Y.%m.%d' 2019.04.08 Have a nice day :) Thomas

Re: date(1) in stretch and buster

On 4/8/19, Étienne Mollier wrote: > On 4/8/19 5:26 PM, Reco wrote: >> Dear list, >> >> the following thing got my attention recently: >> >> stretch$ TZ=UTC date >> Mon Apr 8 15:22:02 UTC 2019 >> buster$ TZ=UTC date >> Mon 08 Apr 2019 03:22:04 PM UTC >> >> It's not that I depend on certain da

Re: date(1) in stretch and buster

On 4/8/19 5:26 PM, Reco wrote: > Dear list, > > the following thing got my attention recently: > > stretch$ TZ=UTC date > Mon Apr 8 15:22:02 UTC 2019 > buster$ TZ=UTC date > Mon 08 Apr 2019 03:22:04 PM UTC > > It's not that I depend on certain date format in scripts, but I got used > to t

Re: date/time of photos SOLVED

On 08/04/2014 08:11 AM Michael Kjörling wrote: On 4 Aug 2014 21:59 +1200, from cbannis...@slingshot.co.nz (Chris Bannister): On Mon, Aug 04, 2014 at 05:08:38AM -0400, ken wrote: It was quite awhile ago, but I used gthumb to offload photos from my Nikon. I didn't like it though because the date&

Re: date/time of photos [was: Re: [SOLVED, but...] mounting a Nikon camera]

2014-08-04 11:08 keltezéssel, ken írta: > It was quite awhile ago, but I used gthumb to offload photos from my > Nikon. I didn't like it though because the date&time of the photos were > all changed to the date&time of the download. I much prefer to keep the > date&time when the photo was taken.

Re: date/time of photos

On 4 Aug 2014 21:59 +1200, from cbannis...@slingshot.co.nz (Chris Bannister): > On Mon, Aug 04, 2014 at 05:08:38AM -0400, ken wrote: >> It was quite awhile ago, but I used gthumb to offload photos from my Nikon. >> I didn't like it though because the date&time of the photos were all changed >> to t

Re: date/time of photos [was: Re: [SOLVED, but...] mounting a Nikon camera]

On Mon, Aug 04, 2014 at 05:08:38AM -0400, ken wrote: > It was quite awhile ago, but I used gthumb to offload photos from my Nikon. > I didn't like it though because the date&time of the photos were all changed > to the date&time of the download. I much prefer to keep the date&time when > the photo

Re: date/time of photos [was: Re: [SOLVED, but...] mounting a Nikon camera]

On 04/08/2014, ken wrote: > It was quite awhile ago, but I used gthumb to offload photos from my > Nikon. I didn't like it though because the date&time of the photos were > all changed to the date&time of the download. I much prefer to keep the > date&time when the photo was taken. What experie

Re: date is wrong

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Oh, sorry. Good that the problem was fixed. It's confusing that K9 mail and Icedove put the original message to the top of inbox, because it's sent at December 2012. Andrei Popescu wrote: >On Jo, 09 feb 12, 12:09:45, Mika Suomalainen wrote: >> H

Re: date is wrong

On Jo, 09 feb 12, 12:09:45, Mika Suomalainen wrote: > Hi, > > Try syncing time from some ntp server. > > First install ntpdate if you do not have it already. > > aptitude install ntp > Then run it > > ntpdate pool.ntp.org > (Run both commands as root.) Your advice is conflicting, since ntpdate i

Re: date is wrong

David Roguin wrote: real date should be Wed Feb 09:32 art 2012 Anyone else experienced something like that? I've tried to manually set the time via gnome settings but nothing happened. The following should sync and set your hardware clock: sudo apt-get install rdate sudo rdate -s timeserver.e

Re: date is wrong

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Try syncing time from some ntp server. First install ntpdate if you do not have it already. > aptitude install ntp Then run it > ntpdate pool.ntp.org (Run both commands as root.) David Roguin wrote: >Hi, > >Today when i boot my notebook, the

Re: date is wrong

On Sun, 2012-12-09 at 09:42 -0300, David Roguin wrote: > Hi, > > Today when i boot my notebook, the date and time is utterly wrong. > > $date > Sun Dec 9 09:39:14 ART 2012 > > real date should be Wed Feb 09:32 art 2012 > > Anyone else experienced something like that? I've tried to manually se

Re: date bug?

Tom Furie writes: > We need a new calendar system... This _has_ been discussed: -- John Hasler -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: date bug?

On Tuesday 01 June 2010 14:32:26 Ron Johnson wrote: > On 06/01/2010 01:41 PM, Boyd Stephen Smith Jr. wrote: > > (It may > > not be entirely friendly, but any other behavior will be hard to reason > > about because of inconsistencies.) > > That's why whomever came up with the complete idiocy of bre

Re: date bug?

On Tue, Jun 01, 2010 at 02:32:26PM -0500, Ron Johnson wrote: > That's why whomever came up with the complete idiocy of breaking up 52 > weeks into 12 irregularly-sized months, days starting in the middle of > the night and years in the middle of winter, should br brought behind the > barn and fl

Re: date bug?

On Jun 1, 2010, at 3:32 PM, Ron Johnson wrote: That's why whomever came up with the complete idiocy of breaking up 52 weeks into 12 irregularly-sized months, days starting in the middle of the night and years in the middle of winter, should br brought behind the barn and flayed alive. Gi

Re: date bug?

On 06/01/2010 01:41 PM, Boyd Stephen Smith Jr. wrote: [snip] Section 6.30, General Rule 6b of the same document reads: "If, after the preceding step, any of the result is outside the permissible range of values for the field or the result is invalid based on the natural rules for dates and tim

Re: date bug?

On Monday 31 May 2010 13:23:30 Ron Johnson wrote: > On 05/31/2010 12:44 PM, Camaleón wrote: > > On Mon, 31 May 2010 17:34:12 +, T o n g wrote: > >> Please take a look at the following, do you think it is bug of date? > >> $ date --date='next month' > >> Thu Jul 1 11:07:31 EDT 2010 > >> > >> I

Re: date bug?

On 05/31/2010 12:44 PM, Camaleón wrote: On Mon, 31 May 2010 17:34:12 +, T o n g wrote: Please take a look at the following, do you think it is bug of date? (...) $ date --date='next month' Thu Jul 1 11:07:31 EDT 2010 I was hoping to get June. But June has not "31 days" so the closes

Re: date bug?

On Mon, 31 May 2010 17:34:12 +, T o n g wrote: > Please take a look at the following, do you think it is bug of date? (...) > $ date --date='next month' > Thu Jul 1 11:07:31 EDT 2010 > > I was hoping to get June. But June has not "31 days" so the closest is indeed "1st July" ;-) > Is it

Re: Date always wrong after reboot. [SOLVED]

Solved it... This wasn't related to the clock at all. I do cut power to the PC when it's off and began wondering if that hat drained the CMOS battery, but that would make BIOS settings reset, not advance the OS clock by one hour. The CMOS time is correct in the BIOS. While checking another issue

Re: Date always wrong after reboot.

On Tue, Jun 02, 2009 at 03:50:49PM +0100, Nuno Magalhães wrote: > I know it's a silly question with a simple answer, but i can't find > the culprit. I've checked /etc/init.d/ and rc2.d/ and there's nothing > that would change the time. However, every time i boot the system > always defaults to one

Re: Date always wrong after reboot.

Nuno Magalhães wrote: > I know it's a silly question with a simple answer, but i can't find > the culprit. I've checked /etc/init.d/ and rc2.d/ and there's nothing > that would change the time. However, every time i boot the system > always defaults to one hour ahead. I assume i can dpkg-reconfigur

Re: Date always wrong after reboot.

On Tue, 2 Jun 2009 15:50:49 +0100 Nuno Magalhães wrote: Hello Nuno, > that would change the time. However, every time i boot the system > always defaults to one hour ahead. I assume i can dpkg-reconfigure > something, but i don't know what. I'd rather not depend on ntp. One possibility is that

Re: date man page

On Sat, May 02, 2009 at 15:12:24 +, T o n g (mlist4sunt...@yahoo.com) wrote: > > Hi, > > I'm wondering where I can find the full man page for the date command. > I've tried the followings, > > date --help > man date > info coreutils 'date invocation' > > But neither give me the help

Re: date - if - bash

On Fri April 17 2009 07:59:39 Erik Xavior wrote: > > why isn't working? :S > > if [ $(date +%H) > 10 ]; then echo "later then 10h"; else echo "before > 10h"; fi; "> 10" created a file called "10". You probably want "-gt 10". --Mike Bird -- To UNSUBSCRIBE, email to debian-user-requ...@li

Re: date - if - bash

it gives an output, yes, but if "date +%H" is smaller then 10, it still says "later then 10h" if [ $(date +%H) > 10 ]; then echo "later then 10h"; else echo "before 10h"; fi;

Re: date - if - bash

On Fri, Apr 17, 2009 at 04:59:39PM +0200, Erik Xavior wrote: > > why isn't working? :S > > if [ $(date +%H) > 10 ]; then echo "later then 10h"; else echo "before 10h"; > fi; because '>' is a string operator? try '-gt' A signature.asc Description: Digital signature

Re: date - if - bash

On Fri, Apr 17, 2009 at 04:59:39PM +0200, Erik Xavior wrote: > > why isn't working? :S > > if [ $(date +%H) > 10 ]; then echo "later then 10h"; else echo "before 10h"; > fi; Because > is a string comparison. Do help test in bash or man test -- "A search of his car uncovered pornograph

Re: date/time problem since kernel change

Hi, > And is your hardware clock actually set to local time? How do you see that exactly (sorry if this a dummy question, but I'm quite lost with local/universal, UTC, CEST, etc.) ? -- Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [E

Re: date/time problem since kernel change

Hi, > And what is the content of "/etc/adjtime"? > I ask, because the behaviour of "hwclock" depends on the contents of > this file (man hwclock). The last line of /etc/adjtime is "LOCAL". In fact, after some Google searching, I wonder if the problem doesn't come from the way the kernel access /

Re: date/time problem since kernel change

Julien Barnier wrote: > | # Set UTC=yes if your system clock is set to UTC (GMT), and UTC=no if not. > | UTC=no And is your hardware clock actually set to local time? -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTE

Re: date/time problem since kernel change

Julien Barnier wrote: > Hi, > >> Are the packages "initscripts" and "tzdata" installed? > > Yes, they are. > >> What is the result of the command >> grep UTC /etc/default/rcS > > Here it is : > > , > | [EMAIL PROTECTED]:~$ grep UTC /etc/default/rcS > | # Set UTC=yes if your system clock

Re: date/time problem since kernel change

Hi, > Are the packages "initscripts" and "tzdata" installed? Yes, they are. > What is the result of the command > grep UTC /etc/default/rcS Here it is : , | [EMAIL PROTECTED]:~$ grep UTC /etc/default/rcS | # Set UTC=yes if your system clock is set to UTC (GMT), and UTC=no if not. | UTC=

Re: date/time problem since kernel change

Julien Barnier wrote: > Hi all, > > I recently switched from an own compiled 2.6.20 kernel to the debian > linux-image-2.6.22 one (I'm using Sid). > > And since I use this new kernel, I get a problem with the time on my > machine : at each reboot I get two hours more than the real time. I'm > qui

Re: date

On Mon, Jun 05, 2006 at 02:51:13PM +0200, Francesco Pietra wrote: [snip] > $date > reports correctly Mon Jun 5 and UTC time, however followed by CEST 2006 > > CEST = Central European Summer Time is misleading, anyway it does not > correspond to the time set and indicated. Really I would like to

Re: Date problem

On Thursday 27 April 2006 23:44, Matthias Julius wrote: > Torquil Macdonald Sørensen <[EMAIL PROTECTED]> writes: > > TZ=CEST didn't have any effect, and /etc/timezone contains a > > line "Europe/Oslo" which is correct. > > Did you export it? Yep, but it didn't affect the time or the timezone repor

Re: Date problem

Torquil Macdonald Sørensen <[EMAIL PROTECTED]> writes: > TZ=CEST didn't have any effect, and /etc/timezone contains a > line "Europe/Oslo" which is correct. Did you export it? > > I have found the problem now by comparing the strace output from the date > command running as root and as tmac. T

Re: Date problem

On Thursday 27 April 2006 20:15, Matthias Julius wrote: > Since when is it doing so? You could try to set TZ=CEST. What is the > content of /etc/timezone? TZ=CEST didn't have any effect, and /etc/timezone contains a line "Europe/Oslo" which is correct. I have found the problem now by comparing

Re: Date problem

TMS writes: > It reports UTC when run as 'tmac', and CEST when run as 'root': What does 'echo $TZ' report when run as 'tmac' and when run as 'root'? -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Date problem

Torquil Macdonald Sørensen <[EMAIL PROTECTED]> writes: > It reports UTC when run as 'tmac', and CEST when run as 'root': > > As root: > tmac:/home/tmac# date > Thu Apr 27 19:50:37 CEST 2006 > > As tmac: > [EMAIL PROTECTED] ~$ date > Thu Apr 27 17:50:49 UTC 2006 Since when is it doing so? You cou

  1   2   >