Olaf Dietsche wrote:
If you go to daylight savings, the clock jumps from 2am to 3am.
No it doesn't. The clock ticks along as it always has done, in UTC. The
timezone simply changes, which should be no big deal for timezone-aware
applications.
The reverse happens, when you go back from
Billy Naylor, 2003-10-06 00:10:14 +0200 :
It appears that cronjobs running between 2am and 3am sunday morning
seem to not have been run, i'm in New Zealand which went into summer
daylight savings over the weekend.
That's strange, because last time I looked, Debian had a specially
patched cron
Hi
I've got a rather wierd problem. Since this morning, I cannot connect
anymore to a pop mail server using ssl, evolution complains about a bad
signature of the certificate. This is since I've booted my machine
today.
At the same time, one minute before I got the after-startup report from
On Mon, Oct 06, 2003 at 05:31:05PM +0100, Andreas W?st wrote:
Hmmm, so what? Are these problems somehow tied together? Furthermore,
what is the probability that the system has really been cracked, and the
logcheck message is not a false positive? I wonder, because it's not a
server machine, it
On Mon, 06 Oct 2003, Noah L. Meyerhans wrote:
You don't have much evidence that it's a security issue at this point.
Logcheck's active system attack messages rarely indicate such a thing.
Don't do anything drastic like reinstall the system until you've got
better evidence that you've been
On Mon, Oct 06, 2003 at 10:07:23PM +0100, Andreas W?st wrote:
I hope you've got some more ideas. I'm strictly following all the
security updates, and have a light mix of woody and sid packages.
run 'shutdown -rF now'
See if the problem persists after the fsck. If it does, check the
files
Hi Noah
Thanks a lot for your fast answer!
On Montag, 06-Okt-03 at 17:58:10, Noah L. Meyerhans wrote:
On Mon, Oct 06, 2003 at 05:31:05PM +0100, Andreas W?st wrote:
Hmmm, so what? Are these problems somehow tied together? Furthermore,
what is the probability that the system has really been
Can anyone help me ID who is trying to hack my system?
This is no hacking, 'cause a true hacker wouldn't spend his time on it.
I know that i may sound trollish and off-topic and will be cursed to the
buffer overflow hell, but this is the kind of thing that the $#!t-head ppl
of press loves to
Hi Noah
Thanks again for your answer!!
On Montag, 06-Okt-03 at 22:13:32, Noah L. Meyerhans wrote:
On Mon, Oct 06, 2003 at 10:07:23PM +0100, Andreas W?st wrote:
I hope you've got some more ideas. I'm strictly following all the
security updates, and have a light mix of woody and sid packages.
Billy Naylor said on Mon, Oct 06, 2003 at 11:04:37AM +1300:
Hi
It appears that cronjobs running between 2am and 3am sunday morning
seem to not have been run, i'm in New Zealand which went into summer
daylight savings over the weekend.
Has anyone else seen this problem?
I think this only
On Tue, 2003-10-07 at 12:09, Mark Ferlatte wrote:
Billy Naylor said on Mon, Oct 06, 2003 at 11:04:37AM +1300:
Hi
It appears that cronjobs running between 2am and 3am sunday morning
seem to not have been run, i'm in New Zealand which went into summer
daylight savings over the weekend.
Olaf Dietsche wrote:
If you go to daylight savings, the clock jumps from 2am to 3am.
No it doesn't. The clock ticks along as it always has done, in UTC. The
timezone simply changes, which should be no big deal for timezone-aware
applications.
The reverse happens, when you go back from
Billy Naylor, 2003-10-06 00:10:14 +0200 :
It appears that cronjobs running between 2am and 3am sunday morning
seem to not have been run, i'm in New Zealand which went into summer
daylight savings over the weekend.
That's strange, because last time I looked, Debian had a specially
patched cron
Hi
I've got a rather wierd problem. Since this morning, I cannot connect
anymore to a pop mail server using ssl, evolution complains about a bad
signature of the certificate. This is since I've booted my machine
today.
At the same time, one minute before I got the after-startup report from
On Mon, Oct 06, 2003 at 05:31:05PM +0100, Andreas W?st wrote:
Hmmm, so what? Are these problems somehow tied together? Furthermore,
what is the probability that the system has really been cracked, and the
logcheck message is not a false positive? I wonder, because it's not a
server machine, it
On Mon, 06 Oct 2003, Noah L. Meyerhans wrote:
You don't have much evidence that it's a security issue at this point.
Logcheck's active system attack messages rarely indicate such a thing.
Don't do anything drastic like reinstall the system until you've got
better evidence that you've been
On Mon, Oct 06, 2003 at 10:07:23PM +0100, Andreas W?st wrote:
I hope you've got some more ideas. I'm strictly following all the
security updates, and have a light mix of woody and sid packages.
run 'shutdown -rF now'
See if the problem persists after the fsck. If it does, check the
files
Hi Noah
Thanks a lot for your fast answer!
On Montag, 06-Okt-03 at 17:58:10, Noah L. Meyerhans wrote:
On Mon, Oct 06, 2003 at 05:31:05PM +0100, Andreas W?st wrote:
Hmmm, so what? Are these problems somehow tied together? Furthermore,
what is the probability that the system has really been
Hi Noah
Thanks again for your answer!!
On Montag, 06-Okt-03 at 22:13:32, Noah L. Meyerhans wrote:
On Mon, Oct 06, 2003 at 10:07:23PM +0100, Andreas W?st wrote:
I hope you've got some more ideas. I'm strictly following all the
security updates, and have a light mix of woody and sid packages.
Billy Naylor said on Mon, Oct 06, 2003 at 11:04:37AM +1300:
Hi
It appears that cronjobs running between 2am and 3am sunday morning
seem to not have been run, i'm in New Zealand which went into summer
daylight savings over the weekend.
Has anyone else seen this problem?
I think this only
On Tue, 2003-10-07 at 12:09, Mark Ferlatte wrote:
Billy Naylor said on Mon, Oct 06, 2003 at 11:04:37AM +1300:
Hi
It appears that cronjobs running between 2am and 3am sunday morning
seem to not have been run, i'm in New Zealand which went into summer
daylight savings over the weekend.
21 matches
Mail list logo
