Hello all,

I've searched through the forum and over the net, and not found anything on this. I'm not saying that information doesn't exist, I may just not be looking in the right place. Anyhow, here's what's going on:

I'll start syslogd, and it logs messages appropriately until midnight, at which time it stops logging altogether. Sending a kill -SIGHUP 'cat /var/..' doesn't fix it, but sending a kill -HUP 5633 [syslogd's pid] gets it working and logging everything as it should, until midnight, then it stops again.

I've looked through my syslogd.conf files for any obvious errors and didn't find any. My system date and time are correct. I'm fairly new to Linux, and thus, fairly stupid about many things. Anyone have any ideas about what might be causing syslogd to stop working as the date changes every day? Any ideas what I might do to stop this happening, or to automate a work around in the mean time?

Thanks in advance,

ptp

When you say it stops, do you mean that no syslogs appear after 00:00 according to the system clock? Or do you mean that syslogd actually enters the T state (stopped via SIGSTOP - Ctrl-Z in bash).

I mean that no longs appear after 00:00. To test this I've intentionally made remote connection requests on ports I've blocked with my firewall, which should make entries via syslog, but no dice until I send the kill -HUP... I'm afraid I don't even know what the "T" state is.... Sorry for my ignorance, thanks for your attempts at helping me.

no longs=no logs.... I can't type...

That is VERY weird. It's not something I've ever experienced before. Are you sure that syslogd is configured correctly, and that you aren't trying to do some off-the-wall whacko thing with it?

Nope, not sure at all that I'm not having it do some weird, off the wall thing. Can you refer to me a place where I can see a copy of a standard, basic, syslogd.conf file, and I'll check that out?