Hello David, thanks for this patch. It has now been added to the latest patch set.
Thanks especially for ensuring the help doc was up to date with your new arg too. Cheers. On Wednesday 27 October 2010 07:19:35 am David Zych wrote: > restartWrapper is wonderful for protecting against the possibility of a > fluke crash, but if something gets legitimately broken that a restart > *can't* fix, I don't want to be inundated with email every few seconds. > So I have modified restartWrapper to also accept a -min_interval > parameter which specifies the minimum time that must elapse between two > successive restarts (defaults to zero if not provided). > > So "restartWrapper -delay 1 -min_interval 300 prog" will restart prog > either 1 second after the previous run stopped OR 5 minutes after the > previous run started, whichever is later. > > The attached patch is against the Radiator 4.7 version of > restartWrapper. Hopefully others will find it helpful too. > > David -- Mike McCauley [email protected] Open System Consultants Pty. Ltd 9 Bulbul Place Currumbin Waters QLD 4223 Australia http://www.open.com.au Phone +61 7 5598-7474 Fax +61 7 5598-7070 Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc. _______________________________________________ radiator mailing list [email protected] http://www.open.com.au/mailman/listinfo/radiator
