[Reportbug-maint] 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 camerontnor...@gmail.com 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

[Reportbug-maint] 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 bi...@debian.org 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

[Reportbug-maint] 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 mo...@debian.org wrote: Hi Michael et al, On Mon, Nov 3, 2014 at 1:19 PM, Michael Biebl bi...@debian.org 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

[Reportbug-maint] 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 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

[Reportbug-maint] 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 the

[Reportbug-maint] 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

[Reportbug-maint] 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 cor...@debian.org 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

[Reportbug-maint] 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 cor...@debian.org wrote: with the appearance of multiple init systems, it might be helpful to know about the currently running init system in the information

[Reportbug-maint] 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 cor...@debian.org wrote: On

[Reportbug-maint] 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