> Why do something so complex? You could instead run milter-greylist in > the foreground inside an infinite loop, putting whatever else you like > in the loop for notification and other cleanup, e.g. > > #!/bin/sh > > while true; do > ...some stuff... > /usr/local/bin/milter-greylist -D > ...some stuff... > done & > > If an infinite loop makes you nervous, you can create some safety that > will exit the loop in the event of something like 5 relaunches in the > space of 5 seconds. > > Better than periodically checking the process table, IMHO. > > Cheers, > > - Joel Sure, you can do this way too... The main point is to have notification about the re-lunch of milter-greylist, since it is a major event which should not go unnoticed. Bests, Attila
Message
RE: [milter-greylist] Crash of 4.0a [Was: Errors in sendmail with 4.0a1]
2007-05-28 by attila.bruncsak@itu.int