On Mon, Nov 3, 2014 at 12:56 PM, Michael Biebl <bi...@debian.org> wrote: > Am 03.11.2014 um 13:21 schrieb Sandro Tosi: >> Hello, >> sorry for resurrecting this post from such a long ago. >> >> On Fri, Mar 21, 2014 at 9:19 PM, Sandro Tosi <mo...@debian.org> wrote: >>> Ok, I think we need a wider audience - what d-d thinks about it? bonus >>> points if - in case we come out to add init info to every bug report - >>> a proper way to retrieve the init running is provided :) > > Such tests have already been provided in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741930#25 > which reflect the recommendation of the systemd and upstart maintainers.
what is the recommended way to identify sysvinit? from the info provided above one requires to check a dir existence and the checking a command and then execute it to parse its output. it seems a bit fragile, and maybe only upstart check really the running processes Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cab4xwxy8ivs9up-slirukazsy4zumwqzso5lh98k-0umwuw...@mail.gmail.com
