Package: cereal Version: 0.22-1 Severity: normal I am running a backport of cereal to Debian etch, with a backport of runit 1.9.0-1.
Sometimes, after destroying a session, runsv and run processes stay around: For example: $ sudo cereal-admin destroy scyf00191 scyh00167 scyh00204 scyr00548 scys00592 scys00593 Really destroy session 'scyf00191'? [Y|n]: y Service cereal.scyf00191 removed, the service daemon received the TERM and CONT signals. Session 'scyf00191' destroyed. Really destroy session 'scyh00167'? [Y|n]: y Service cereal.scyh00167 removed, the service daemon received the TERM and CONT signals. Session 'scyh00167' destroyed. Really destroy session 'scyh00204'? [Y|n]: y Service cereal.scyh00204 removed, the service daemon received the TERM and CONT signals. Session 'scyh00204' destroyed. Session 'scyr00548' is currently running. Really stop and destroy session? [Y|n]: y yok: down: /var/lib/cereal/sessions/scyr00548: 0s, normally up Service cereal.scyr00548 removed, the service daemon received the TERM and CONT signals. Session 'scyr00548' stopped and destroyed. Really destroy session 'scys00592'? [Y|n]: Service cereal.scys00592 removed, the service daemon received the TERM and CONT signals. Session 'scys00592' destroyed. Really destroy session 'scys00593'? [Y|n]: y Service cereal.scys00593 removed, the service daemon received the TERM and CONT signals. Session 'scys00593' destroyed. $ pstree -ap <snip> ├─runsvdir,1605 -P /etc/service... │ ├─runsv,1994 cereal.scyf00191 │ │ └─run,1995 -e ./run │ ├─runsv,2203 cereal.scys00592 │ │ └─run,2204 -e ./run │ ├─runsv,2207 cereal.scys00593 │ │ └─run,2208 -e ./run │ ├─runsv,2210 cereal.scyh00167 │ │ └─run,2211 -e ./run │ └─runsv,2282 cereal.scyh00204 │ └─run,2283 -e ./run I do not know whether this is a cereal issue or a runit issue. Greetings Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
