[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: not starting packages at boot

On Sun, Jan 23, 2005 at 11:10:37AM +0100, Goswin von Brederlow wrote:
> Marc Haber <mh+debian-devel@zugschlus.de> writes:

> > On Sat, 22 Jan 2005 18:44:16 -0800, Steve Langasek <vorlon@debian.org>
> > wrote:
> >>I hope that at least the cupsys maintainer will close this bug without
> >>mangling the package in this fashion; there's no reason to have the cupsys
> >>server package installed if you're not going to use it as a server.
> >
> > I disagree. I have a number of server packages installed on my
> > personal laptop for the sake of having the docs with me. I am,
> > however, fine with using update-rc.d or $EDITOR /etc/runlevel.conf[1]
> > to accomplish this.
> >
> > My beef is that I want to be able to prevent a newly installed
> > package's postinst from starting the service (for example, because I
> > know that the service needs configuration before it can be started for
> > the first time, or because I know that this service is probably never
> > going to run on this installation).
> >
> > Greetings
> > Marc

> > [1] Thanks, Roland, for file-rc, which is really great

> Chroots also nearly never want to start services and it would be nice
> fi there were a consistent way to stop daemons from getting started
> (stoped on upgrade) on install there.

echo -e '#!/bin/sh\n\nexit 101' > /chroot/usr/sbin/policy-rc.d \
&& chmod a+x /chroot/usr/sbin/policy-rc.d

Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature

Reply to: