On Tue, Jun 12, 2007 at 06:53:04PM +0200, Robert Felber wrote: > On Tue, Jun 12, 2007 at 03:34:06PM +0200, Til Obes wrote: > > Robert Felber schrieb: > > >Despair: > > >use (bz|z)grep "policyd-weight\[" /var/log/* | \ > > > grep -v "(decided|weighted)" > > >Unfortunately there is no strict standard how to log stuff, and each OS > > >logs > > >a little bit different (der Teufel ist ein Eichhoernchen). So grep all your > > >logs which may exist in /var/log (and subdirectories) for policyd-weight > > >messages and grep out (-v) "decided" and "weighted" messages. > > > > Ok i found something: > > Jun 5 11:20:59 mailhost postfix/policyd-weight[13463]: child: spawned > > Jun 5 11:21:03 mailhost postfix/policyd-weight[13463]: warning: ignoring > > garbage: TEST > > Jun 5 11:21:04 mailhost postfix/policyd-weight[13463]: fatal_exit: > > unrecognized request type: '' > > Jun 5 11:21:04 mailhost postfix/policyd-weight[13463]: child: err: fatal: > > unrecognized request type: '' at > > /usr/local/bin/policyd-weight line 690, <GEN7> line 2. > > Jun 5 11:21:04 mailhost postfix/policyd-weight[13303]: child 13463 exited > > This is normal and not the cause.
[...] > > Currently I can think only of some situations where a "crash" without > logging could happen: > > - Signals like KILL, INT, TERM, QUIT, PIPE (and other sigs which cause > termination) > are not logged. Try http://www.policyd-weight.org/policyd-weight-devel This is still an unofficial version (0.1.14 beta-6) I have added signal handlers for most of critical signals. However, they don't attempt to recover from the signals, they only provide logging. -- Robert Felber (PGP: 896CF30B) Munich, Germany ____________________________________________________________ Policyd-weight Mailinglist - http://www.policyd-weight.org/
