On Wed, Aug 22, 2007 at 17:05:53 +0100, Chris Buckley wrote:
>> Had to run dpkg-reconfigure tzdata. It had me in Central Europe. :-(
>
> What's bizarre is on our Debian 3.1 install, when i run apt-get install
> --reinstall tzdata, it says package not found.
>
> A dpkg -l | grep tzdata returns no
Giorgos Pallas wrote:
# apt-cache search tzdata
Package not found. Was wondering whether 3.1 is like Ubuntu 6.06 where
locales incorporates tzdata (scheduled to be changed in the next stable
releaser in 09 iirc..)
Problem is solved now though - sysklogd just needed restarting - *doh!*
--
Just a quick update:
I've resolved this without a reboot.
/etc/init.d/sysklogd restart
..did the trick. syslog/cron now picks up the,correct, time.
Thanks for all the replies, and I hope this helps someone else :)
--
Kind Regards, ::T: +44(0)1223 446093 C: +44(0)7779 268173
Chris Buc
Appears a reboot fixes the issue!
I tried HUP'ing syslogd, but this didn't work :(
Any ideas why a reboot was required - seems a bit overkill..
--
Kind Regards, ::T: +44(0)1223 446093 C: +44(0)7779 268173
Chris Buckley ::Systems Administration and Security, UNIX.
Netbanx, Ltd.
Chris Buckley wrote:
>> Had to run dpkg-reconfigure tzdata. It had me in Central Europe. :-(
>
> What's bizarre is on our Debian 3.1 install, when i run apt-get
> install --reinstall tzdata, it says package not found.
>
> A dpkg -l | grep tzdata returns nothing either.
>
> I'm very stumped on thi
Had to run dpkg-reconfigure tzdata. It had me in Central Europe. :-(
What's bizarre is on our Debian 3.1 install, when i run apt-get install
--reinstall tzdata, it says package not found.
A dpkg -l | grep tzdata returns nothing either.
I'm very stumped on this problem :(
--
Kind Regards,
Chris Buckley([EMAIL PROTECTED]) is reported to have said:
> Hi,
>
> A very strange problem has cropped up on our Debian GNU/Linux 3.1 box this
> morning.
>
> We have a crontab for a user scheduled to run at:
>
> 45 4 * * * /path/to/utils/script-executed.pl
> 2>/path/to/logs/stdout-foobar.lo
Chris Buckley wrote:
Giorgos D. Pallas wrote:
I had exactly the same problem a couple of days ago. I was surprised to
find out that the /usr/share/zoneinfo/ mplah mplah file which defines my
timezone was damaged (don't know how...). I replaced it and all was fine
again...
So, my suggestion, try
Giorgos D. Pallas wrote:
I had exactly the same problem a couple of days ago. I was surprised to
find out that the /usr/share/zoneinfo/ mplah mplah file which defines my
timezone was damaged (don't know how...). I replaced it and all was fine
again...
So, my suggestion, try to reinstall tzdata..
Chris Buckley wrote:
> Douglas A. Tutty wrote:
>> Is the system clock set to UTC? $ cat /etc/default/rcS
>>
>> You should see a line
>> UTC=yes.
>
> A good point. It currently reads:
>
> UTC=no
>
>> I don't know if this matters, and with a tz of London it shouldn't
>> account for 5 hrs.
>
> Agreed
Douglas A. Tutty wrote:
Is the system clock set to UTC?
$ cat /etc/default/rcS
You should see a line
UTC=yes.
A good point. It currently reads:
UTC=no
I don't know if this matters, and with a tz of London it shouldn't
account for 5 hrs.
Agreed. It's certainly a very bizarre problem, an
On Wed, Aug 22, 2007 at 10:08:52AM +0100, Chris Buckley wrote:
>
> A very strange problem has cropped up on our Debian GNU/Linux 3.1 box
> this morning.
>
> We have a crontab for a user scheduled to run at:
>
> 45 4 * * * /path/to/utils/script-executed.pl
> 2>/path/to/logs/stdout-foobar.l
Hi,
A very strange problem has cropped up on our Debian GNU/Linux 3.1 box
this morning.
We have a crontab for a user scheduled to run at:
45 4 * * * /path/to/utils/script-executed.pl
2>/path/to/logs/stdout-foobar.log
The cron.log shows this file running at "04:45".
Aug 22 04:45:01 nb
13 matches
Mail list logo
