Re: [opensuse] restarting X server in openSUSE 12.2 with systemd

jdd said the following on 09/12/2013 11:04 AM:

Le 12/09/2013 15:26, Patrick Shanahan a écrit :

...

* jdd [09-12-13 03:49]:

...

...

"rcmulti" and "rcgraphical" could be much more friendly

But they have been, rcsshd {start,stop,restart,status,...} init {S,1,3,5,6} still perform as expected via replacement scripts linking to the actual systemctl command syntax.

yes, with a little less informations

in fact these commands say "redirecting to systemd", if they could give the hole systemctl command, this would be a learning process :-)

I think you misunderstand. Look at the inode number of the init command and the systemd command On my system, 12.3 its a symlink $ ls -li /sbin/init 125001 lrwxrwxrwx 1 root root 26 Sep 10 18:41 /sbin/init -> ../usr/lib/systemd/systemd That means when you think you are executing "init 3" what actually happens is the equivalent of char *argv[] = { "init", "3", NULL }; execve("/usr/lib/systemd/systemd", argv, environ); Then systemd looks at argv[0] and sees that its invocation 'name" -- from the command line -- is "init" but as you will see if you read 'man 1 init', it checks it PID to see it it is 1. It can't be because you've just invoked it, so For compatibility with SysV, if systemd is called as init and a PID that is not 1, it will execute telinit and pass all command line arguments unmodified. That means init and telinit are mostly equivalent when invoked from normal login sessions. See telinit(8) for more information. I think that adequately answers your question. -- How long did the whining go on when KDE2 went on KDE3? The only universal constant is change. If a species can not adapt it goes extinct. That's the law of the universe, adapt or die. -- Billie Walsh, May 18 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org