Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #172093

Re: Systemd and Init was Problems communicating with and between servers after upgrade - correction

From Greg Wooledge <wooledg@eeg.ccf.org>
Newsgroups linux.debian.user
Subject Re: Systemd and Init was Problems communicating with and between servers after upgrade - correction
Date 2016-09-12 21:20 +0200
Message-ID <sgEVQ-7xR-37@gated-at.bofh.it> (permalink)
References <sfgsz-3pz-61@gated-at.bofh.it> <sfgsz-3pz-59@gated-at.bofh.it> <sgEsN-76N-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Mon, Sep 12, 2016 at 07:32:52PM +0100, Clive Menzies wrote:
> However, studying documentation on systemd v init, I'm a bit confused. I 
> assumed the reinstall would implement systemd for all services and init 
> wouldn't be visible although symlinks will use init where necessary. 
> systemd-sysv is installed as per the Debian wiki.

Most of the common server-oriented packages in jessie have systemd
units written for them.  E.g. openssh-server:

~$ dpkg -L openssh-server | grep systemd
/lib/systemd
/lib/systemd/system
/lib/systemd/system/ssh.service
/lib/systemd/system/ssh.socket
/lib/systemd/system/ssh@.service

However, there are still several packages that were not updated to use
systemd facilities in time for jessie.  These packages still ship with
sysvinit scripts.

When a given service has sysvinit script and does *not* have systemd
unit files, it falls back to the sysvinit scripts.

> Looking at other setups on the net, a ps aux should assign the first 
> process (1) to systemd but on server_M it is /sbin/init
> 
> Is this right?

The kernel still runs /sbin/init because the systemd changes are not
intrusive all the way up inside the kernel.  Thus, the kernel does not
know or care which init system you're using.

On a jessie-systemd (default) installation, /sbin/init is a symlink:

~$ ls -ld /sbin/init
lrwxrwxrwx 1 root root 20 Mar 12  2016 /sbin/init -> /lib/systemd/systemd

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Re: Problems communicating with and between servers after upgrade -  correction Clive Menzies <clive@clivemenzies.co.uk> - 2016-09-09 01:00 +0200
  Re: Problems communicating with and between servers after upgrade -  correction Clive Menzies <clive@clivemenzies.co.uk> - 2016-09-09 10:20 +0200
    Re: Problems communicating with and between servers after upgrade -  correction Clive Menzies <clive@clivemenzies.co.uk> - 2016-09-09 10:30 +0200
  Systemd and Init was Problems communicating with and between servers  after upgrade - correction Clive Menzies <clive@clivemenzies.co.uk> - 2016-09-12 20:50 +0200
    Re: Systemd and Init was Problems communicating with and between servers after upgrade - correction Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-12 21:20 +0200
      Re: Systemd and Init was Problems communicating with and between  servers after upgrade - correction Clive Menzies <clive@clivemenzies.co.uk> - 2016-09-12 22:30 +0200

csiph-web