Shorewall users - Jan 2003 - shorewall ( and everything else) quit logging

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have a machine that is running Shorewall 1.3.11a. Last night it
quit all logging. The "messages" file just ends at 4:20 PM, no
entries since. I was vim''n into that file about that time.... Any
ideas how to start logging without a reboot? 
Thanks for your time,
Steve Postma
Sys Admin
Travizon

-----BEGIN PGP SIGNATURE-----
Version: PGP 7.1

iQA/AwUBPjfelH7faP1rMljoEQIxiQCg4pGIAzcmCbwulkyzTxelvA1BJYMAoNim
jwGX6l/boes9mmssEX38qMjP
=RcFF
-----END PGP SIGNATURE-----

--On Wednesday, January 29, 2003 9:00 AM -0500 Steve Postma 
<spostma@travizon.com> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have a machine that is running Shorewall 1.3.11a. Last night it
> quit all logging. The "messages" file just ends at 4:20 PM, no
> entries since. I was vim''n into that file about that time.... Any
> ideas how to start logging without a reboot?
> Thanks for your time,
You can try restarting syslogd/klogd.

-Tom
--
Tom Eastep   \ Shorewall - iptables made easy
Shoreline,    \ http://www.shorewall.net
Washington USA \ teastep@shorewall.net

> I have a machine that is running Shorewall 1.3.11a. Last night it
> quit all logging. The "messages" file just ends at 4:20
Make sure you haven''t run out of drive space in whatever partition (or
ramdisk) receives your log. If you have, free up some room and then, as Tom
suggested, restart syslogd.

dvt