Re: having a problem with multilog not shutting down...
Jeremy Hansen <[email protected]> Tue, 29 Jan 2013 01:09:13 -0800
| Newsgroups | gmane.comp.djb.syslog |
|---|---|
| Message-ID | <[email protected]> |
Thanks. This works as far as making sure that multilog gets killed, but = I'm curious about your statement regarding multilog waiting for a = newline. Is this a problem with the application or is there something I = can do to test this theory and fix it? Thanks -jeremy On Jan 28, 2013, at 8:52 PM, Peter Wolfenden <[email protected]> = wrote: > Hi Jeremy, >=20 > The svc-stop.sh script appears to support a -k option, which is = supposed kill the service if SIGTERM doesn't stop it: >=20 > = https://github.com/bruceg/supervise-scripts/blob/master/svc-stop.sh >=20 > This could help it a situation where multilog is stuck waiting for a = newline. >=20 > Cheers, >=20 > Peter >=20 > On Mon, Jan 28, 2013 at 8:24 PM, Andy Bradford = <[email protected]> wrote: > Thus said Jeremy Hansen on Mon, 28 Jan 2013 20:10:48 -0800: >=20 > > Point is, svc -d doesn't bring it down either, so it's not the = script. > > What will cause a process to not die using svc -d? >=20 > Well, the process will receive SIGTERM, and the documentation (which = you > can find here: http://cr.yp.to/daemontools/multilog.html ) says = this > about SIGTERM: >=20 > If multilog receives a TERM signal, it will read and process data > until the next newline, and then exit, leaving stdin at the first > byte of data it has not processed. >=20 > Andy >=20 >=20 >=20 >=20 > --=20 > Peter Wolfenden > 650-801-7714