On Fri, 06 Apr 2001, Steve Greenland wrote:
> On 06-Apr-01, 11:41 (CDT), Damian M Gryski <[EMAIL PROTECTED]> wrote:
> >
> > So, this for me pretty much nails it that something is borked with the
> > sysklogd cron.weekly script.
>
> I'd guess that the daemon wasn't restarted after the logs were rotated,
> so that all the messages since have been written to whereever those file
> descriptors point. You could poke around in /proc/(syslogdpid)/fd, or
> just run /etc/init.d/sysklogd restart.
Nope, because the problem is persistent across reboots. So, even a
freshly started syslogd isn't writing to the logfiles.
Damian
--
Damian Gryski ==> [EMAIL PROTECTED] | Linux, the choice of a GNU generation
512 pt Hacker Test score = 37% | 500 pt Nerd Test score = 56%
geek / linux zealot / coder / juggler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
