Processing commands for cont...@bugs.debian.org:
> tags 738759 + patch
Bug #738759 [initscripts] /etc/init.d/rc: adding/removing init scripts during
runlevel switch results in double/no run for specific init scripts
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you
tags 738759 + patch
thanks
Hi!
Please find attach a proposed patch for the issue. I hope we can get
around at work to test it properly within the next few days, but from
what I can tell this should be a good approach.
Enjoy,
Rhonda
--
Fühlst du dich mutlos, fass endlich Mut, los |
Control: tags -1 pending
On 13 February 2014 21:18, Helmut Grohne wrote:
> Control: retitle -1 initscripts: Skip killing root-owned process starting
> with @
>
> On Thu, Feb 13, 2014 at 08:58:33PM +, Dimitri John Ledkov wrote:
>> How about limiting it to processes running as root?
>>
>> E.g.
Processing control commands:
> tags -1 pending
Bug #738855 [initscripts] initscripts: Skip killing root-owned process starting
with @
Added tag(s) pending.
--
738855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
I managed to get my machine to boot again by adding "init=/bin/bash" as
kernel parameter, and then
mount -o remount,rw /
chmod -x /etc/init.d/bootlogd
What I don't understand is:
root@(none):/# /etc/rcS.d/S03mountdevsubfs.sh start
root@(none):/# /etc/rcS.d/S04bootlogd start
root@(none):/# /etc/
Processing control commands:
> retitle -1 initscripts: Skip killing root-owned process starting with @
Bug #738855 [initscripts] initscripts: Skip killing process starting with @
Changed Bug title to 'initscripts: Skip killing root-owned process starting
with @' from 'initscripts: Skip killing pr
Control: retitle -1 initscripts: Skip killing root-owned process starting with @
On Thu, Feb 13, 2014 at 08:58:33PM +, Dimitri John Ledkov wrote:
> How about limiting it to processes running as root?
>
> E.g. pgrep -u root -f "^@" ?
>
> That way there is no loop-hole opened, since those proc
On 13 February 2014 15:05, Helmut Grohne wrote:
> Hi Dimitri,
>
> On Thu, Feb 13, 2014 at 01:58:23PM +, Dmitrijs Ledkovs wrote:
>> There is convention starting that processes whos name starts with '@'
>> shouldn't be killed. It is used to indicate that process is needed to
>> manage root devic
Am Donnerstag, 13. Februar 2014, 11:11:26 schrieb Petter Reinholdtsen:
> I've tried to reproduce this part of your problem report:
> > * What was the outcome of this action?
> > Cannot install initscripts after installing insserv 1.16 because it
> > tries to connect to systemd which is present on t
Hi Dimitri,
On Thu, Feb 13, 2014 at 01:58:23PM +, Dmitrijs Ledkovs wrote:
> There is convention starting that processes whos name starts with '@'
> shouldn't be killed. It is used to indicate that process is needed to
> manage root device / cleanly unmount the root filesystem.
>
> At least md
Package: initscripts
Version: 2.88dsf-41
Severity: normal
Tags: patch
Dear Maintainer,
There is convention starting that processes whos name starts with '@'
shouldn't be killed. It is used to indicate that process is needed to
manage root device / cleanly unmount the root filesystem.
At least md
Your message dated Thu, 13 Feb 2014 11:05:01 +
with message-id
and subject line Bug#703833: fixed in sysvinit 2.88dsf-51
has caused the Debian Bug report #703833,
regarding tmpfs.5: /tmp is not mounted as tmpfs by default in this
to be marked as done.
This means that you claim that the proble
Your message dated Thu, 13 Feb 2014 11:05:01 +
with message-id
and subject line Bug#686701: fixed in sysvinit 2.88dsf-51
has caused the Debian Bug report #686701,
regarding /usr/share/man/man5/rcS.5: add fsck.5 to the the list in SEE ALSO
to be marked as done.
This means that you claim that t
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 13 Feb 2014 11:51:12 +0100
Source: sysvinit
Binary: sysvinit sysvinit-core sysvinit-utils sysv-rc initscripts bootlogd
Architecture: source amd64 all
Version: 2.88dsf-51
Distribution: unstable
Urgency: low
Maintainer
sysvinit_2.88dsf-51_amd64.changes uploaded successfully to localhost
along with the files:
sysvinit_2.88dsf-51.dsc
sysvinit_2.88dsf-51.debian.tar.xz
sysvinit_2.88dsf-51_amd64.deb
sysvinit-core_2.88dsf-51_amd64.deb
sysvinit-utils_2.88dsf-51_amd64.deb
sysv-rc_2.88dsf-51_all.deb
initscri
I've tried to reproduce this part of your problem report:
> * What was the outcome of this action?
> Cannot install initscripts after installing insserv 1.16 because it
> tries to connect to systemd which is present on the system but not
> used as PID 1.
I have no problem installing initscripts o
16 matches
Mail list logo
