Results 1 to 3 of 3

Thread: prevent dpkg from (re-)starting services

  1. #1
    Join Date
    May 2008
    Beans
    6

    Question prevent dpkg from (re-)starting services

    Hi!

    I'm using hardy on a fileserver. In the exported directory there are several ubuntu versions used as root filesystem for thin clients, e.g. hardy-i386, hardy-amd64 which I installed via debootstrap. I chroot into their directories to install new packages, updates etc. The problem is, that every time I install the update of a service, the service is restarted in the chrooted environment.

    Is there a way to prevent dpkg from restarting these services?

    Thanks in advance!

  2. #2
    Join Date
    May 2008
    Beans
    6

    Re: prevent dpkg from (re-)starting services

    Perhaps the problem is a bit misunderstanding:

    The chrooted environment shall not run any service, but whenever I install an update of e.g. cups, cups is started.

    Deleting the services from /etc/rc* directories is not an option, as they
    are needed by the clients.

  3. #3
    Join Date
    May 2008
    Beans
    6

    Re: prevent dpkg from (re-)starting services

    Hi!

    Just got a mail from Michael Biebl at debian-user and the suggested script seems to work fine.

    policy-rc.d to your rescue.

    Read the man page of invoke-rc.d : "INIT SCRIPT POLICY"
    and /usr/share/doc/sysv-rc/README.policy-rc.d.gz

    A simple /usr/sbin/policy-rc.d could look like this:

    # cat /usr/sbin/policy-rc.d
    #!/bin/sh
    echo "************************************" >&2
    echo "All rc.d operations denied by policy" >&2
    echo "************************************" >&2
    exit 101

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •