On Mon, Mar 2, 2015 at 11:16 AM, Laurent Bercot <[email protected]> wrote: > On 02/03/2015 05:40, Neale Pickett wrote: >> >> I'm running runsvdir as PID 1 > > > Hi Neale, > runsvdir is actually not intended to be run as process 1. > runit's model is to have the "runit" program itself run as process 1, > and it spawns a program for every stage: /etc/runit/{1, 2, 3}. > Traditionally, people use runsvdir in stage 2; when runit gets a > SIGINT, it kills runsvdir then enters stage 3. > See http://smarden.org/runit/runit.8.html > > I'm not sure how different from upstream the busybox version of > runit is, but they shouldn't be too far apart. The intent in > busybox runit is probably to have runsvdir run under busybox init.
Well, some people did want runsvdir as PID 1, and bbox has a little extension for it, -s SCRIPT. I do not want people to be forced to use a particular init. Neale is right, we forgot to intercept SIGINT and pass it to SCRIPT. Fixed in git. _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
