From: James Nessen (nessenj@jimsoffice.org)
Date: Fri Jul 14 2000 - 14:54:09 PDT
It did it to me once as well, but try doing a syslog stop wait a few
seconds and then do a syslog start and it should working again, for some
reason HUP'in it causes it to puke.
Jim
Quoting John Cassella (redpaw@mvfx.com) [00.07.14 11:30]:
> Liam,
>
> Actually I'm running redhat and I have the same problem with my syslog
> after the logs rotate once a week the syslog demon stops logging and I get a
> weird error sometimes
> in my root mailbox from cron. something along the lines of cron telling me
> "logrotate: no command in rc.1 " or something like that (not in front of the
> machine now)
> I haven't had time to troubleshoot it yet tho... I just do the following by
> hand for now (gasp!!)
> what usually helps to get it to log again for me is just to restart the
> syslog daemon and then restart pmfirewall
> you could set it up as another cron job or something if it helps until you
> really figure out what the real problem is...
>
> sorry I can't be of more help but i'm in the same boat as you are
> - redpaw
****************************************************************************
* To UNSUBSCRIBE from the list, send a message with "unsubscribe pmfirewall"
* in the message body to majordomo@pointman.org. Please direct other
* questions, comments, or problems to pmfirewall-owner@pointman.org.
*
* Need answers fast? Check the list archive located at:
* http://www.pointman.org/PMFirewall/list-archive/
*
This archive was generated by hypermail 2b29 : Sun Jun 10 2001 - 02:35:23 PDT