Bug#741930: Re: Bug#741930: reportbug: add current init system information

2014-11-08 Thread Steve Langasek
On Sat, Nov 08, 2014 at 10:15:46AM +, Jonathan de Boyne Pollard wrote: > There isn't really a reliable way to identify any of these as the current > running system, and upstart is not checking the running processes either. > * To check for upstart as the running system manager, one checks

Bug#741930: reportbug: add current init system information

2014-11-08 Thread Cameron Norman
On Wed, Nov 5, 2014 at 3:10 AM, Sandro Tosi wrote: > Hello, > > On Wed, Nov 5, 2014 at 1:09 AM, Cameron Norman > wrote: >> A few notes I have: >> >> 1. With Jessie and on, with sysvinit /sbin/init //will// be a link, >> not the true init file. This would lead to unknowns when the init was >> act

Bug#741930: Re: Bug#741930: reportbug: add current init system information

2014-11-08 Thread Jonathan de Boyne Pollard
Sandro Tosi: 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 There

Bug#741930: reportbug: add current init system information

2014-11-05 Thread Sandro Tosi
Hello, On Wed, Nov 5, 2014 at 1:09 AM, Cameron Norman wrote: > A few notes I have: > > 1. With Jessie and on, with sysvinit /sbin/init //will// be a link, > not the true init file. This would lead to unknowns when the init was > actually sysv. care to explain a bit better? I just upgraded a Whee

Bug#741930: reportbug: add current init system information

2014-11-04 Thread Cameron Norman
On Tue, Nov 4, 2014 at 5:35 AM, Sandro Tosi wrote: > Hi Michael et al, > > On Mon, Nov 3, 2014 at 1:19 PM, Michael Biebl wrote: >>> 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 on

Bug#741930: reportbug: add current init system information

2014-11-04 Thread Sandro Tosi
Hi Michael et al, On Mon, Nov 3, 2014 at 1:19 PM, Michael Biebl wrote: >> 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 > > The system

Bug#741930: reportbug: add current init system information

2014-11-03 Thread Michael Biebl
Hi Sandro, Am 03.11.2014 um 14:07 schrieb Sandro Tosi: > what is the recommended way to identify sysvinit? I don't think there is. I'd simply assume sysvinit is the active init if the tests for upstart and systemd fail. from the info > provided above one requires to check a dir existence and th

Bug#741930: reportbug: add current init system information

2014-11-03 Thread Sandro Tosi
Hello, sorry for resurrecting this post from such a long ago. On Fri, Mar 21, 2014 at 9:19 PM, Sandro Tosi 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 r

Bug#741930: reportbug: add current init system information

2014-09-06 Thread Laurent Bigonville
Package: reportbug Version: 6.5.1 Followup-For: Bug #741930 Hi, Any news about this? I think this can be a very valuable information when trying to debug issues that touch to user sessions (polkit, xDM programs,...) and integration with logind. Cheers, Laurent Bigonville -- To UNSUBSCRIBE,

Bug#741930: reportbug: add current init system information

2014-03-21 Thread Michael Biebl
Am 21.03.2014 22:19, schrieb Sandro Tosi: > a proper way to retrieve the init running is provided :)> - systemd The canonical check for systemd being PID 1 is [ -d /run/systemd/system ] See also man 3 sd_booted and [0] - upstart For upstart the canonical check is defined in /lib/lsb/init-functi

Bug#741930: reportbug: add current init system information

2014-03-21 Thread Sandro Tosi
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 :) cheers, Sandro On Fri, Mar 21, 2014 at 10:15 PM, Yves-Alexis Perez wrote: > On Fri, Mar 21, 2014

Bug#741930: reportbug: add current init system information

2014-03-21 Thread Yves-Alexis Perez
On Fri, Mar 21, 2014 at 10:00:12PM +0100, Sandro Tosi wrote: > Hello Yves-Alexis > > On Mon, Mar 17, 2014 at 12:00 PM, Yves-Alexis Perez wrote: > > with the appearance of multiple init systems, it might be helpful to > > know about the currently running init system in the information > > collecte

Bug#741930: reportbug: add current init system information

2014-03-21 Thread Sandro Tosi
Hello Yves-Alexis On Mon, Mar 17, 2014 at 12:00 PM, Yves-Alexis Perez wrote: > with the appearance of multiple init systems, it might be helpful to > know about the currently running init system in the information > collected by reportbug. > > A quick idea would be to report the result of: > > re

Bug#741930: reportbug: add current init system information

2014-03-17 Thread Yves-Alexis Perez
Package: reportbug Version: 6.5.0 Severity: wishlist Hi, with the appearance of multiple init systems, it might be helpful to know about the currently running init system in the information collected by reportbug. A quick idea would be to report the result of: readlink /proc/1/exe but that won