Re: [opensuse-factory] Runlevels in 12.1?
Okay, maybe I'm missing something in this long debate..but, what exactly is the problem here? systemctl doesn't have the same concept of runlevels as sysvinit init 3 used to be a convenient way of booting a system that had X installed without loading X systemctl disable xdm.service is arguably just as easy a way of accomplishing the same thing with systemd, with systemctl start xdm.service being how you'd start X when you want it, systemctl stop xdm.service being how to stop it when you're done with it.. Am I missing something here?
Rüdiger Meier 11/12/11 2:32 PM >>> Sry for messing up the thread, my MUA was fighting against me.
On Saturday 12 November 2011, Carlos E. R. wrote:
On Saturday, 2011-11-12 at 14:58 +0100, Rüdiger Meier wrote:
3. If you don't use any feature of kdm at all why you should use it then? Speaking for me I don't use any kdm feature except typing my password whitch works even better without kdm.
ConsoleKit. It needs the login manager. Once I had a bugzilla where I could not hibernate, and that was the reason.
If this is true then it's another bad example for the more and more evil dependency hell. Why on earth one should need a login manager just to hibernate the machine? cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2011-11-12 at 14:42 -0000, Richard Brown wrote:
Okay, maybe I'm missing something in this long debate..but, what exactly is the problem here?
That we do not know how to do things now. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6+j98ACgkQtTMYHG2NR9Us4ACfbslqEIBsbzAhnaiM5ckgzh3t oRwAn2O5ojnOdrEC3YnJC9rOsWwtrzVy =Lw2L -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/12/2011 09:42 AM, Richard Brown pecked at the keyboard and wrote:
Okay, maybe I'm missing something in this long debate..but, what exactly is the problem here?
systemctl doesn't have the same concept of runlevels as sysvinit
init 3 used to be a convenient way of booting a system that had X installed without loading X
systemctl disable xdm.service is arguably just as easy a way of accomplishing the same thing with systemd, with systemctl start xdm.service being how you'd start X when you want it, systemctl stop xdm.service being how to stop it when you're done with it..
Am I missing something here?
The only thing missing is the education of the masses. And the fact that the "new" way of doing this is so much easier then using init 3 & init 5. :-) Maybe I'll create a couple of new aliases like: alias init3="systemctl stop xdm.service" alias init5="systemctl start xdm.service" -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
The only thing missing is the education of the masses.
And the fact that the "new" way of doing this is so much easier then using init 3 & init 5. Maybe I'll create a couple of new aliases like:
alias init3="systemctl stop xdm.service" alias init5="systemctl start xdm.service" I wonder then if we should include those aliases by default...
On Saturday, November 12, 2011 11:02:28 AM Ken Schneider - openSUSE wrote: probably with a small blurb,"This is actually such and such doing that thing it does," when its used so the user will be aware of the change. -- "I'd love to go out with you, but the man on television told me to stay tuned." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday 12 November 2011, Roger Luedecke wrote:
On Saturday, November 12, 2011 11:02:28 AM Ken
Schneider - openSUSE wrote:
The only thing missing is the education of the masses.
And the fact that the "new" way of doing this is so much
easier then
using init 3 & init 5. Maybe I'll create a couple of new aliases like:
alias init3="systemctl stop xdm.service" alias init5="systemctl start xdm.service"
I wonder then if we should include those aliases by default...
But please don't bother non-systemd users with such defaults. It would be similar to the messed up insserv command https://bugzilla.novell.com/show_bug.cgi?id=728947 cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le 12/11/2011 17:02, Ken Schneider - openSUSE a écrit :
The only thing missing is the education of the masses.
you are right
And the fact that the "new" way of doing this is so much easier then using init 3 & init 5. :-) Maybe I'll create a couple of new aliases like:
alias init3="systemctl stop xdm.service" alias init5="systemctl start xdm.service"
is that really what happen? one thing disturbing is that kernel command line option X and init X do not seems anymore to gibe the same result. The true fact is that people that used to make doc do'nt know the technology and people that do the technology don't have time to make notes. I'm sure we will meet soon :-)) jdd -- http://www.dodin.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2011-11-12 at 19:09 +0100, jdd wrote:
alias init3="systemctl stop xdm.service"
Ah, this one works.
alias init5="systemctl start xdm.service"
The funny thing is that "init 5" does work. Why not init 3?
is that really what happen? one thing disturbing is that kernel command line option X and init X do not seems anymore to gibe the same result.
Pff
The true fact is that people that used to make doc do'nt know the technology and people that do the technology don't have time to make notes. I'm sure we will meet soon :-))
I really hope. I made a bugzilla because the openSUSE book doesn't document systemd. Meanwhile I think I'l keep using what I know. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6/JIQACgkQtTMYHG2NR9Wo0gCcCc64QJ52UATlFQch9MujKOUs 7moAnj/0TXjbj5d23gPmmo9WyOVtVBeL =mfjr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/12/2011 08:59 PM, Carlos E. R. pecked at the keyboard and wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Saturday, 2011-11-12 at 19:09 +0100, jdd wrote:
alias init3="systemctl stop xdm.service"
Ah, this one works.
alias init5="systemctl start xdm.service"
The funny thing is that "init 5" does work. Why not init 3?
is that really what happen? one thing disturbing is that kernel command line option X and init X do not seems anymore to gibe the same result.
Pff
The true fact is that people that used to make doc do'nt know the technology and people that do the technology don't have time to make notes. I'm sure we will meet soon :-))
I really hope. I made a bugzilla because the openSUSE book doesn't document systemd.
Meanwhile I think I'l keep using what I know.
At least the choice is there at boot time, option F5 I believe. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2011-11-12 at 23:03 -0500, Ken Schneider - openSUSE wrote:
At least the choice is there at boot time, option F5 I believe.
I'll use the permanent workaround, I think. Here http://en.opensuse.org/openSUSE:Most_annoying_bugs_12.1#Upgrade it says: Upgrade Bug #725917 System is switched from sysvinit to systemd while upgrade. The workaround is to install the sysvinit-init package. As soon as its install gets acknowledged the removal of the systemd-sysvinit package will be suggested. Perhaps I would prefer to have it installed but inactive, like when using the F5 key. But they don't comment that option there. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6/ukMACgkQtTMYHG2NR9VYDQCfd9cvmn2mzGQLP4ky9WTW6GfD oRUAn11zp0JWAye1l5M8A+Yphl+WwJqC =ER++ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, Nov 13, 2011 at 01:38:27PM +0100, Carlos E. R. wrote: [ 8< ]
I'll use the permanent workaround, I think.
Here http://en.opensuse.org/openSUSE:Most_annoying_bugs_12.1#Upgrade it says:
Upgrade
Bug #725917 System is switched from sysvinit to systemd while upgrade. The workaround is to install the sysvinit-init package. As soon as its install gets acknowledged the removal of the systemd-sysvinit package will be suggested.
Perhaps I would prefer to have it installed but inactive, like when using the F5 key. But they don't comment that option there.
The suggested workaround keeps the packages systemd and systemd-presets-branding-openSUSE installed. It's currently impossible to remove them. At the end /sbin/init must point to something. Adding an additional new sysconfig setting or an additional command to switch between both would cause extra work which might not be payed off due to the limited time (I hope) it would be of use. But submit requests are as always more than welcome. And you have read bnc#725917? If I get it right the suggestion made by Ludwig with comment 3 would have made the pain in the case of an upgrade less big. Unfortunately nobody cared earlier. Luckily this thread must end in three days as with the release of openSUSE 12.1 any further discussion then belongs to the general opensuse list. :) @Jdd: Thanx for your reply even on the wrong list. From the list archive you know whome you have to smack for the distraction. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2011-11-13 at 14:54 +0100, Lars Müller wrote:
On Sun, Nov 13, 2011 at 01:38:27PM +0100, Carlos E. R. wrote:
[ 8< ]
I'll use the permanent workaround, I think.
Here http://en.opensuse.org/openSUSE:Most_annoying_bugs_12.1#Upgrade it says:
Upgrade
Bug #725917 System is switched from sysvinit to systemd while upgrade. The workaround is to install the sysvinit-init package. As soon as its install gets acknowledged the removal of the systemd-sysvinit package will be suggested.
Perhaps I would prefer to have it installed but inactive, like when using the F5 key. But they don't comment that option there.
The suggested workaround keeps the packages systemd and systemd-presets-branding-openSUSE installed. It's currently impossible to remove them.
Ok.
At the end /sbin/init must point to something. Adding an additional new sysconfig setting or an additional command to switch between both would cause extra work which might not be payed off due to the limited time (I hope) it would be of use. But submit requests are as always more than welcome.
And you have read bnc#725917? If I get it right the suggestion made by Ludwig with comment 3 would have made the pain in the case of an upgrade less big.
Yes, I read it.
Unfortunately nobody cared earlier. Luckily this thread must end in three days as with the release of openSUSE 12.1 any further discussion then belongs to the general opensuse list. :)
True. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6/0hAACgkQtTMYHG2NR9X9kgCfYpzOX0+LBjP0Q6ae78bM5l4q iMUAn352ZzvKSU7V2eLKa/g7cv50HjM1 =NNir -----END PGP SIGNATURE-----
Ken Schneider - openSUSE wrote:
alias init3="systemctl stop xdm.service" alias init5="systemctl start xdm.service"
I just tried an experiment. I started my computer with "3" at the grub prompt, which brought me to a console session where I could log in as a mere muggle. I then tried to use the above to start the desktop and found I first had to become root. Why can't a user start the desktop as could be done with startx? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2011-11-12 at 15:04 -0500, James Knott wrote:
then tried to use the above to start the desktop and found I first had to become root. Why can't a user start the desktop as could be done with startx?
That is so since 11.4. Change this: /etc/permissions.local # setuid bit on Xorg is only needed if no display manager, ie startx # is used. Beware of CVE-2010-2240. # #/usr/bin/Xorg root:root 4711 - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6+2tMACgkQtTMYHG2NR9VU0ACggsK6QVnACYS7EKPj/AoRF8A4 3K0An16uhuSG93lvte39jv1Yyqz213zX =v35M -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2011/11/12 14:42 (GMT) Richard Brown composed:
Okay, maybe I'm missing something in this long debate..but, what exactly is the problem here?
systemctl doesn't have the same concept of runlevels as sysvinit
init 3 used to be a convenient way of booting a system that had X installed without loading X
systemctl disable xdm.service is arguably just as easy a way of accomplishing the same thing with systemd, with systemctl start xdm.service being how you'd start X when you want it, systemctl stop xdm.service being how to stop it when you're done with it..
Am I missing something here?
Convenience disappeared, unless systemctl is aliased to what used to work (& easy to remember, easy to convey in help forums) somehow: #runlevel S 5 init 3 <- 6 characters vs. systemctl stop xdm.service <- 26 characters, 333% more init 5 <- 6 characters vs. systemctl start xdm.service <- 27 characters, 350% more #runlevel S 5 init 2 <- 6 characters (kill: XDM, NFS, Samba, Apache, etc) vs. systemctl ???...??? (Lord only knows how many more characters to do all the above) Until easy to find, easy to understand systemd docs are universally available like those for init, I'm not going to begin learning how to switch from easy to complicated, sticking with sysvinit until then. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday 12 November 2011 13:21:08 Felix Miata wrote:
Convenience disappeared, unless systemctl is aliased to what used to work (& easy to remember, easy to convey in help forums) somehow:
#runlevel S 5 init 3 <- 6 characters vs. systemctl stop xdm.service <- 26 characters, 333% more
Am I missing something crucial here? # rcxdm status redirecting to systemctl xdm.service - LSB: X Display Manager Loaded: loaded (/etc/init.d/xdm) Active: active (running) since Tue, 08 Nov 2011 13:14:26 +0100; 4 days ago CGroup: name=systemd:/system/xdm.service ├ 3780 /usr/bin/kdm ├ 23922 /usr/bin/Xorg -br :0 vt7 -nolisten tcp -auth /var/lib/xdm/authdir/authfiles/A:0-1jE1La ├ 23926 -:0 └ 23927 /usr/lib64/kde4/libexec/kdm_greet # init 3 # rcxdm status redirecting to systemctl xdm.service - LSB: X Display Manager Loaded: loaded (/etc/init.d/xdm) Active: inactive (dead) since Sat, 12 Nov 2011 19:31:18 +0100; 1s ago Process: 26816 ExecStop=/etc/init.d/xdm stop (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/xdm.service seems to me that "init 3" works now just as well as it did before Anders -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le 12/11/2011 19:32, Anders Johansson a écrit :
seems to me that "init 3" works now just as well as it did before
not always. init being a binary, I don't know how to trace what he does in systemd system to understand why it don't always works jdd -- http://www.dodin.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday 12 November 2011, jdd wrote:
Le 12/11/2011 19:32, Anders Johansson a écrit :
seems to me that "init 3" works now just as well as it did before
not always. init being a binary, I don't know how to trace what he does in systemd system to understand why it don't always works
strace -f init 3 cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
not always. init being a binary, I don't know how to trace what he does in systemd system to understand why it don't always works
strace -f init 3
Looks like greek to me. Elanor:~ # strace -f init 3 execve("/sbin/init", ["init", "3"], [/* 61 vars */]) = 0 brk(0) = 0x6d9000 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f42c093a000 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 fstat(3, {st_mode=S_IFREG|0644, st_size=91304, ...}) = 0 mmap(NULL, 91304, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f42c0923000 close(3) = 0 open("/lib64/libselinux.so.1", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260^\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=118064, ...}) = 0 mmap(NULL, 2217728, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f42c04fd000 mprotect(0x7f42c0519000, 2093056, PROT_NONE) = 0 mmap(0x7f42c0718000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1b000) = 0x7f42c0718000 mmap(0x7f42c071a000, 1792, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f42c071a000 close(3) = 0 open("/lib64/libdbus-1.so.3", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\201\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=282368, ...}) = 0 mmap(NULL, 2378240, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f42c02b8000 mprotect(0x7f42c02fb000, 2097152, PROT_NONE) = 0 mmap(0x7f42c04fb000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x43000) = 0x7f42c04fb000 close(3) = 0 open("/lib64/libudev.so.0", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\3403\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=64304, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f42c0922000 mmap(NULL, 2159344, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f42c00a8000 mprotect(0x7f42c00b7000, 2093056, PROT_NONE) = 0 mmap(0x7f42c02b6000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xe000) = 0x7f42c02b6000 close(3) = 0 open("/lib64/libwrap.so.0", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0207\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=40928, ...}) = 0 mmap(NULL, 2139496, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f42bfe9d000 mprotect(0x7f42bfea6000, 2093056, PROT_NONE) = 0 mmap(0x7f42c00a5000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x8000) = 0x7f42c00a5000 mmap(0x7f42c00a7000, 1384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f42c00a7000 close(3) = 0 open("/lib64/libpam.so.0", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\300*\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=56048, ...}) = 0 mmap(NULL, 2150992, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f42bfc8f000 mprotect(0x7f42bfc9c000, 2093056, PROT_NONE) = 0 mmap(0x7f42bfe9b000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xc000) = 0x7f42bfe9b000 close(3) = 0 open("/lib64/libaudit.so.1", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360(\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=96296, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f42c0921000 mmap(NULL, 2191424, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f42bfa77000 mprotect(0x7f42bfa8e000, 2093056, PROT_NONE) = 0 mmap(0x7f42bfc8d000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x16000) = 0x7f42bfc8d000 close(3) = 0 open("/lib64/libcap.so.2", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\220\26\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=19024, ...}) = 0 mmap(NULL, 2114120, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f42bf872000 mprotect(0x7f42bf876000, 2093056, PROT_NONE) = 0 mmap(0x7f42bfa75000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7f42bfa75000 close(3) = 0 open("/lib64/librt.so.1", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\200\"\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=42777, ...}) = 0 mmap(NULL, 2128912, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f42bf66a000 mprotect(0x7f42bf671000, 2093056, PROT_NONE) = 0 mmap(0x7f42bf870000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6000) = 0x7f42bf870000 close(3) = 0 open("/lib64/libc.so.6", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\23\2\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=1871381, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f42c0920000 mmap(NULL, 3730344, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f42bf2db000 mprotect(0x7f42bf460000, 2097152, PROT_NONE) = 0 mmap(0x7f42bf660000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x185000) = 0x7f42bf660000 mmap(0x7f42bf665000, 19368, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f42bf665000 close(3) = 0 open("/lib64/libdl.so.2", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\r\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=19053, ...}) = 0 mmap(NULL, 2109688, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f42bf0d7000 mprotect(0x7f42bf0d9000, 2097152, PROT_NONE) = 0 mmap(0x7f42bf2d9000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7f42bf2d9000 close(3) = 0 open("/lib64/libpthread.so.0", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260l\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=136155, ...}) = 0 mmap(NULL, 2212768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f42beeba000 mprotect(0x7f42beed2000, 2093056, PROT_NONE) = 0 mmap(0x7f42bf0d1000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x17000) = 0x7f42bf0d1000 mmap(0x7f42bf0d3000, 13216, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f42bf0d3000 close(3) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f42c091f000 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f42c091e000 mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f42c091c000 arch_prctl(ARCH_SET_FS, 0x7f42c091c7c0) = 0 mprotect(0x7f42bf660000, 16384, PROT_READ) = 0 mprotect(0x7f42bf0d1000, 4096, PROT_READ) = 0 mprotect(0x7f42bf2d9000, 4096, PROT_READ) = 0 mprotect(0x7f42bf870000, 4096, PROT_READ) = 0 mprotect(0x7f42bfa75000, 4096, PROT_READ) = 0 mprotect(0x7f42bfc8d000, 4096, PROT_READ) = 0 mprotect(0x7f42bfe9b000, 4096, PROT_READ) = 0 mprotect(0x7f42c00a5000, 4096, PROT_READ) = 0 mprotect(0x7f42c02b6000, 4096, PROT_READ) = 0 mprotect(0x7f42c04fb000, 4096, PROT_READ) = 0 mprotect(0x7f42c0718000, 4096, PROT_READ) = 0 mprotect(0x6cb000, 49152, PROT_READ) = 0 mprotect(0x7f42c093b000, 4096, PROT_READ) = 0 munmap(0x7f42c0923000, 91304) = 0 set_tid_address(0x7f42c091ca90) = 19366 set_robust_list(0x7f42c091caa0, 0x18) = 0 futex(0x7ffffd066d9c, FUTEX_WAKE_PRIVATE, 1) = 0 futex(0x7ffffd066d9c, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, NULL, 7f42c091c7c0) = -1 EAGAIN (Resource temporarily unavailable) rt_sigaction(SIGRTMIN, {0x7f42beec0720, [], SA_RESTORER|SA_SIGINFO, 0x7f42beec9d00}, NULL, 8) = 0 rt_sigaction(SIGRT_1, {0x7f42beec07b0, [], SA_RESTORER|SA_RESTART|SA_SIGINFO, 0x7f42beec9d00}, NULL, 8) = 0 rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0 statfs("/selinux", {f_type="EXT2_SUPER_MAGIC", f_bsize=4096, f_blocks=2580222, f_bfree=1716819, f_bavail=1585735, f_files=656640, f_ffree=529712, f_fsid={1833917818, -2091677103}, f_namelen=255, f_frsize=4096}) = 0 brk(0) = 0x6d9000 brk(0x6fa000) = 0x6fa000 open("/proc/filesystems", O_RDONLY) = 3 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f42c0939000 read(3, "nodev\tsysfs\nnodev\trootfs\nnodev\tb"..., 1024) = 343 read(3, "", 1024) = 0 close(3) = 0 munmap(0x7f42c0939000, 4096) = 0 execve("/bin/systemctl", ["init", "3"], [/* 61 vars */]) = 0 brk(0) = 0x62d000 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ffbcd970000 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) open("/usr/lib64/tls/x86_64/libselinux.so.1", O_RDONLY) = -1 ENOENT (No such file or directory) stat("/usr/lib64/tls/x86_64", 0x7fffb23c6d10) = -1 ENOENT (No such file or directory) open("/usr/lib64/tls/libselinux.so.1", O_RDONLY) = -1 ENOENT (No such file or directory) stat("/usr/lib64/tls", 0x7fffb23c6d10) = -1 ENOENT (No such file or directory) open("/usr/lib64/x86_64/libselinux.so.1", O_RDONLY) = -1 ENOENT (No such file or directory) stat("/usr/lib64/x86_64", 0x7fffb23c6d10) = -1 ENOENT (No such file or directory) open("/usr/lib64/libselinux.so.1", O_RDONLY) = -1 ENOENT (No such file or directory) stat("/usr/lib64", {st_mode=S_IFDIR|0755, st_size=49152, ...}) = 0 open("/etc/ld.so.cache", O_RDONLY) = 3 fstat(3, {st_mode=S_IFREG|0644, st_size=91304, ...}) = 0 mmap(NULL, 91304, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7ffbcd959000 close(3) = 0 open("/lib64/libselinux.so.1", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260^\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=118064, ...}) = 0 mmap(NULL, 2217728, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7ffbcd533000 mprotect(0x7ffbcd54f000, 2093056, PROT_NONE) = 0 mmap(0x7ffbcd74e000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1b000) = 0x7ffbcd74e000 mmap(0x7ffbcd750000, 1792, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7ffbcd750000 close(3) = 0 open("/usr/lib64/libcap.so.2", O_RDONLY) = -1 ENOENT (No such file or directory) open("/lib64/libcap.so.2", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\220\26\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=19024, ...}) = 0 mmap(NULL, 2114120, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7ffbcd32e000 mprotect(0x7ffbcd332000, 2093056, PROT_NONE) = 0 mmap(0x7ffbcd531000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7ffbcd531000 close(3) = 0 open("/usr/lib64/libsystemd-daemon.so.0", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\200\r\0\0\0\0\0\0"..., 832) = 832 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ffbcd958000 fstat(3, {st_mode=S_IFREG|0755, st_size=14640, ...}) = 0 mmap(NULL, 2109648, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7ffbcd12a000 mprotect(0x7ffbcd12c000, 2097152, PROT_NONE) = 0 mmap(0x7ffbcd32c000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7ffbcd32c000 close(3) = 0 open("/usr/lib64/libdbus-1.so.3", O_RDONLY) = -1 ENOENT (No such file or directory) open("/lib64/libdbus-1.so.3", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\201\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=282368, ...}) = 0 mmap(NULL, 2378240, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7ffbccee5000 mprotect(0x7ffbccf28000, 2097152, PROT_NONE) = 0 mmap(0x7ffbcd128000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x43000) = 0x7ffbcd128000 close(3) = 0 open("/usr/lib64/librt.so.1", O_RDONLY) = -1 ENOENT (No such file or directory) open("/lib64/librt.so.1", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\200\"\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=42777, ...}) = 0 mmap(NULL, 2128912, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7ffbcccdd000 mprotect(0x7ffbccce4000, 2093056, PROT_NONE) = 0 mmap(0x7ffbccee3000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6000) = 0x7ffbccee3000 close(3) = 0 open("/usr/lib64/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory) open("/lib64/libc.so.6", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\23\2\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=1871381, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ffbcd957000 mmap(NULL, 3730344, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7ffbcc94e000 mprotect(0x7ffbccad3000, 2097152, PROT_NONE) = 0 mmap(0x7ffbcccd3000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x185000) = 0x7ffbcccd3000 mmap(0x7ffbcccd8000, 19368, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7ffbcccd8000 close(3) = 0 open("/lib64/libdl.so.2", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\r\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=19053, ...}) = 0 mmap(NULL, 2109688, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7ffbcc74a000 mprotect(0x7ffbcc74c000, 2097152, PROT_NONE) = 0 mmap(0x7ffbcc94c000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7ffbcc94c000 close(3) = 0 open("/lib64/libpthread.so.0", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260l\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=136155, ...}) = 0 mmap(NULL, 2212768, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7ffbcc52d000 mprotect(0x7ffbcc545000, 2093056, PROT_NONE) = 0 mmap(0x7ffbcc744000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x17000) = 0x7ffbcc744000 mmap(0x7ffbcc746000, 13216, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7ffbcc746000 close(3) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ffbcd956000 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ffbcd955000 mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ffbcd953000 arch_prctl(ARCH_SET_FS, 0x7ffbcd9537c0) = 0 mprotect(0x7ffbcccd3000, 16384, PROT_READ) = 0 mprotect(0x7ffbcc744000, 4096, PROT_READ) = 0 mprotect(0x7ffbcc94c000, 4096, PROT_READ) = 0 mprotect(0x7ffbccee3000, 4096, PROT_READ) = 0 mprotect(0x7ffbcd128000, 4096, PROT_READ) = 0 mprotect(0x7ffbcd32c000, 4096, PROT_READ) = 0 mprotect(0x7ffbcd531000, 4096, PROT_READ) = 0 mprotect(0x7ffbcd74e000, 4096, PROT_READ) = 0 mprotect(0x62b000, 4096, PROT_READ) = 0 mprotect(0x7ffbcd971000, 4096, PROT_READ) = 0 munmap(0x7ffbcd959000, 91304) = 0 set_tid_address(0x7ffbcd953a90) = 19366 set_robust_list(0x7ffbcd953aa0, 0x18) = 0 futex(0x7fffb23c75bc, FUTEX_WAKE_PRIVATE, 1) = 0 futex(0x7fffb23c75bc, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, NULL, 7ffbcd9537c0) = -1 EAGAIN (Resource temporarily unavailable) rt_sigaction(SIGRTMIN, {0x7ffbcc533720, [], SA_RESTORER|SA_SIGINFO, 0x7ffbcc53cd00}, NULL, 8) = 0 rt_sigaction(SIGRT_1, {0x7ffbcc5337b0, [], SA_RESTORER|SA_RESTART|SA_SIGINFO, 0x7ffbcc53cd00}, NULL, 8) = 0 rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0 statfs("/selinux", {f_type="EXT2_SUPER_MAGIC", f_bsize=4096, f_blocks=2580222, f_bfree=1716819, f_bavail=1585735, f_files=656640, f_ffree=529712, f_fsid={1833917818, -2091677103}, f_namelen=255, f_frsize=4096}) = 0 brk(0) = 0x62d000 brk(0x64e000) = 0x64e000 open("/proc/filesystems", O_RDONLY) = 3 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ffbcd96f000 read(3, "nodev\tsysfs\nnodev\trootfs\nnodev\tb"..., 1024) = 343 read(3, "", 1024) = 0 close(3) = 0 munmap(0x7ffbcd96f000, 4096) = 0 lstat("/sys/fs/cgroup", {st_mode=S_IFDIR|0755, st_size=260, ...}) = 0 lstat("/sys/fs/cgroup/systemd", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 stat("/proc/1/root", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat("/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat("/proc/1/root", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat("/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 lstat("/sys/fs/cgroup", {st_mode=S_IFDIR|0755, st_size=260, ...}) = 0 lstat("/sys/fs/cgroup/systemd", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 geteuid() = 0 socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC, 0) = 3 connect(3, {sa_family=AF_FILE, path="/run/systemd/private"}, 22) = 0 fcntl(3, F_GETFL) = 0x2 (flags O_RDWR) fcntl(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0 geteuid() = 0 getsockname(3, {sa_family=AF_FILE, NULL}, [2]) = 0 getsockopt(3, SOL_SOCKET, SO_PEERCRED, {pid=1, uid=0, gid=0}, [12]) = 0 poll([{fd=3, events=POLLOUT}], 1, 90000) = 1 ([{fd=3, revents=POLLOUT}]) sendto(3, "\0", 1, MSG_NOSIGNAL, NULL, 0) = 1 sendto(3, "AUTH EXTERNAL 30\r\n", 18, MSG_NOSIGNAL, NULL, 0) = 18 poll([{fd=3, events=POLLIN}], 1, 90000) = 1 ([{fd=3, revents=POLLIN}]) read(3, "OK 581621e96ee78e1ab08a929b00000"..., 2048) = 37 poll([{fd=3, events=POLLOUT}], 1, 90000) = 1 ([{fd=3, revents=POLLOUT}]) sendto(3, "NEGOTIATE_UNIX_FD\r\n", 19, MSG_NOSIGNAL, NULL, 0) = 19 poll([{fd=3, events=POLLIN}], 1, 90000) = 1 ([{fd=3, revents=POLLIN}]) read(3, "AGREE_UNIX_FD\r\n", 2048) = 15 poll([{fd=3, events=POLLOUT}], 1, 90000) = 1 ([{fd=3, revents=POLLOUT}]) sendto(3, "BEGIN\r\n", 7, MSG_NOSIGNAL, NULL, 0) = 7 gettid() = 19366 mmap(NULL, 548864, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ffbcd8cd000 sendmsg(3, {msg_name(0)=NULL, msg_iov(2)=[{"l\1\0\1$\0\0\0\1\0\0\0\240\0\0\0\1\1o\0\31\0\0\0/org/fre"..., 176}, {"\20\0\0\0runlevel3.target\0\0\0\0\7\0\0\0isol"..., 36}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 212 poll([{fd=3, events=POLLIN}], 1, 25000) = 1 ([{fd=3, revents=POLLIN}]) recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"l\2\1\1'\0\0\0\1\0\0\0\17\0\0\0\5\1u\0\1\0\0\0\10\1g\0\1o\0\0"..., 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 71 recvmsg(3, 0x7fffb23c6e90, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable) sendmsg(3, {msg_name(0)=NULL, msg_iov(2)=[{"l\1\0\1\25\0\0\0\2\0\0\0\227\0\0\0\1\1o\0\31\0\0\0/org/fre"..., 168}, {"\20\0\0\0runlevel3.target\0", 21}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 189 poll([{fd=3, events=POLLIN}], 1, 25000) = 1 ([{fd=3, revents=POLLIN}]) recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"l\4\1\1+\0\0\0\2\0\0\0\203\0\0\0\1\1o\0\31\0\0\0/org/fre"..., 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 284 recvmsg(3, 0x7fffb23c6e90, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable) sendmsg(3, {msg_name(0)=NULL, msg_iov(2)=[{"l\1\0\0019\0\0\0\3\0\0\0\250\0\0\0\1\1o\0004\0\0\0/org/fre"..., 184}, {"\35\0\0\0org.freedesktop.systemd1.Uni"..., 57}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 241 poll([{fd=3, events=POLLIN}], 1, 25000) = 1 ([{fd=3, revents=POLLIN}]) recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"l\4\1\0015\0\0\0\4\0\0\0\223\0\0\0\1\1o\0\31\0\0\0/org/fre"..., 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 221 recvmsg(3, 0x7fffb23c6e90, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable) poll([{fd=3, events=POLLIN}], 1, 24975) = 1 ([{fd=3, revents=POLLIN}]) recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"l\2\1\1\10\0\0\0\5\0\0\0\17\0\0\0\5\1u\0\3\0\0\0\10\1g\0\1v\0\0"..., 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 40 recvmsg(3, 0x7fffb23c6e90, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable) close(3) = 0 exit_group(0) = ? Elanor:~ # - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6+0XYACgkQtTMYHG2NR9X9eACeJ1DKrcUDvOQe0pYicXWz/pne c6YAoJG05gHVNI8KEtOcabaQJe7xRB8F =p9q3 -----END PGP SIGNATURE-----
On Saturday 12 November 2011 21:05:10 Carlos E. R. wrote:
On Saturday, 2011-11-12 at 19:50 +0100, Rüdiger Meier wrote:
strace -f init 3
Looks like greek to me.
The condensed version of your strace reveals the relevant parts [...]
socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC, 0) = 3 connect(3, {sa_family=AF_FILE, path="/run/systemd/private"}, 22) = 0
connecting to systemd
sendto(3, "AUTH EXTERNAL 30\r\n", 18, MSG_NOSIGNAL, NULL, 0) = 18 read(3, "OK 581621e96ee78e1ab08a929b00000"..., 2048) = 37 sendto(3, "NEGOTIATE_UNIX_FD\r\n", 19, MSG_NOSIGNAL, NULL, 0) = 19 read(3, "AGREE_UNIX_FD\r\n", 2048) = 15 sendto(3, "BEGIN\r\n", 7, MSG_NOSIGNAL, NULL, 0) = 7
The hand shake
gettid() = 19366 mmap(NULL, 548864, PROT_READ|PROT_WRITE, MAP_PRIVATE| MAP_ANONYMOUS, -1, 0) = 0x7ffbcd8cd000 sendmsg(3, {msg_name(0)=NULL, msg_iov(2)=[{"l\1\0\1$\0\0\0\1\0\0\0\240\0\0\0\1\1o\0\31\0\0\0/org/fre"..., 176}, {"\20\0\0\0runlevel3.target\0\0\0\0\7\0\0\0isol"..., 36}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 212 poll([{fd=3, events=POLLIN}], 1, 25000) = 1 ([{fd=3, revents=POLLIN}])
Telling systemd to go to runlevel 3
recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"l\2\1\1'\0\0\0\1\0\0\0\17\0\0\0\5\1u\0\1\0\0\0\10\1g\0\1o\0\0 "..., 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 71 recvmsg(3, 0x7fffb23c6e90, MSG_CMSG_CLOEXEC) = -1
This presumably contains the result, but unfortunately only the first few bytes are included in this strace (use -s with some suitably large value to capture the entirety of such strings) I'd say the tool does what it's supposed to, and if it doesn't work, systemd will have to reveal why. Maybe there is a permission problem? Maybe some other error? Doesn't it log anything? Anders -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2011-11-12 at 21:19 +0100, Anders Johansson wrote:
On Saturday 12 November 2011 21:05:10 Carlos E. R. wrote:
Telling systemd to go to runlevel 3
recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"l\2\1\1'\0\0\0\1\0\0\0\17\0\0\0\5\1u\0\1\0\0\0\10\1g\0\1o\0\0 "..., 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 71 recvmsg(3, 0x7fffb23c6e90, MSG_CMSG_CLOEXEC) = -1
This presumably contains the result, but unfortunately only the first few bytes are included in this strace (use -s with some suitably large value to capture the entirety of such strings)
Elanor:~ # strace -o trace -s 200 -f init 3 20126 mmap(NULL, 548864, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fd33e0ea000 20126 sendmsg(3, {msg_name(0)=NULL, msg_iov(2)=[{"l\1\0\1$\0\0\0\1\0\0\0\240\0\0\0\1\1o\0\31\0\0\0/org/freedesktop/systemd1\0\0\0\0\0\0\0\6\1s\0\30\0\0\0org.freedesktop.systemd1\0\0\0\0\0\0\0\0\2\1s\0 \0\0\0org.freedesktop.systemd1.Manager\0\0\0\0\0\0\0\0\3\1s\0\t\0\0\0StartUnit\0\0\0\0\0\0\0\10\1g\0\2ss\0", 176}, {"\20\0\0\0runlevel3.target\0\0\0\0\7\0\0\0isolate\0", 36}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 212 20126 poll([{fd=3, events=POLLIN}], 1, 25000) = 1 ([{fd=3, revents=POLLIN}]) 20126 recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"l\2\1\1'\0\0\0\1\0\0\0\17\0\0\0\5\1u\0\1\0\0\0\10\1g\0\1o\0\0\"\0\0\0/org/freedesktop/systemd1/job/1613\0\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272\272"..., 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 71 20126 recvmsg(3, 0x7fff17724dd0, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable) 20126 sendmsg(3, {msg_name(0)=NULL, msg_iov(2)=[{"l\1\0\1\25\0\0\0\2\0\0\0\227\0\0\0\1\1o\0\31\0\0\0/org/freedesktop/systemd1\0\0\0\0\0\0\0\6\1s\0\30\0\0\0org.freedesktop.systemd1\0\0\0\0\0\0\0\0\2\1s\0 \0\0\0org.freedesktop.systemd1.Manager\0\0\0\0\0\0\0\0\3\1s\0\7\0\0\0GetUnit\0\10\1g\0\1s\0\0", 168}, {"\20\0\0\0runlevel3.target\0", 21}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 189 20126 poll([{fd=3, events=POLLIN}], 1, 25000) = 1 ([{fd=3, revents=POLLIN}]) 20126 recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"l\4\1\1+\0\0\0\2\0\0\0\203\0\0\0\1\1o\0\31\0\0\0/org/freedesktop/systemd1\0\0\0\0\0\0\0\2\1s\0 \0\0\0org.freedesktop.systemd1.Manager\0\0\0\0\0\0\0\0\3\1s\0\6\0\0\0JobNew\0\0\10\1g\0\2uo\0\6\1s\0\n\0\0\0:no-sender\0\0\0\0\0\0M\6\0\0\"\0\0\0/org/freedesktop/systemd1/job/1613\0l\2\1\0019"..., 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 284 20126 recvmsg(3, 0x7fff17724dd0, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable) 20126 sendmsg(3, {msg_name(0)=NULL, msg_iov(2)=[{"l\1\0\0019\0\0\0\3\0\0\0\250\0\0\0\1\1o\0004\0\0\0/org/freedesktop/systemd1/unit/multi_2duser_2etarget\0\0\0\0\6\1s\0\30\0\0\0org.freedesktop.systemd1\0\0\0\0\0\0\0\0\2\1s\0\37\0\0\0org.freedesktop.DBus.Properties\0\3\1s\0\3\0\0\0Get\0\0\0\0\0\10\1g\0\2ss\0", 184}, {"\35\0\0\0org.freedesktop.systemd1.Unit\0\0\0\20\0\0\0NeedDaemonReload\0", 57}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 241 20126 poll([{fd=3, events=POLLIN}], 1, 25000) = 1 ([{fd=3, revents=POLLIN}]) 20126 recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"l\4\1\0015\0\0\0\4\0\0\0\223\0\0\0\1\1o\0\31\0\0\0/org/freedesktop/systemd1\0\0\0\0\0\0\0\2\1s\0 \0\0\0org.freedesktop.systemd1.Manager\0\0\0\0\0\0\0\0\3\1s\0\n\0\0\0JobRemoved\0\0\0\0\0\0\10\1g\0\3uos\0\0\0\0\0\0\0\0\6\1s\0\n\0\0\0:no-sender\0\0\0\0\0\0M\6\0\0\"\0\0\0/org/freedesktop/systemd"..., 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 221 20126 recvmsg(3, 0x7fff17724dd0, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable) 20126 poll([{fd=3, events=POLLIN}], 1, 24971) = 1 ([{fd=3, revents=POLLIN}]) 20126 recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"l\2\1\1\10\0\0\0\5\0\0\0\17\0\0\0\5\1u\0\3\0\0\0\10\1g\0\1v\0\0\1b\0\0\0\0\0\0/systemd1\0\0\0\0\0\0\0\2\1s\0 \0\0\0org.freedesktop.systemd1.Manager\0\0\0\0\0\0\0\0\3\1s\0\n\0\0\0JobRemoved\0\0\0\0\0\0\10\1g\0\3uos\0\0\0\0\0\0\0\0\6\1s\0\n\0\0\0:no-sender\0\0\0\0\0\0M\6\0\0\"\0\0\0/org/freedesktop/systemd"..., 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 40 20126 recvmsg(3, 0x7fff17724dd0, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable) 20126 close(3) = 0 20126 exit_group(0) = ? ~
I'd say the tool does what it's supposed to, and if it doesn't work, systemd will have to reveal why. Maybe there is a permission problem? Maybe some other error? Doesn't it log anything?
There is a lot in the log. I'l take note of the date and repeat "init 3" ... this: Nov 12 21:25:32 Elanor systemd[1]: NetworkManager.service: control process exited, code=exited status=1 Nov 12 21:25:32 Elanor systemd[1]: dev-sda1.swap swap process exited, code=exited status=255 Nov 12 21:25:32 Elanor systemd[1]: Unit dev-sda1.swap entered failed state. It says swap failed, but swap is active. And by the way, when I tried to log in the graphic session, it died and dumped my in text mode - finally! I did again: init 5 init 3 Tried to log in the graphics session, it dies. This is the full log, I don't know what is important. Nov 12 21:25:32 Elanor systemd[1]: NetworkManager.service: control process exited, code=exited status=1 Nov 12 21:25:32 Elanor systemd[1]: dev-sda1.swap swap process exited, code=exited status=255 Nov 12 21:25:32 Elanor systemd[1]: Unit dev-sda1.swap entered failed state. Nov 12 21:27:40 Elanor dhcpcd[4035]: eth0: renewing lease of 192.168.74.131 Nov 12 21:27:41 Elanor ifup: eth0 device: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 01) Nov 12 21:27:41 Elanor SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... Nov 12 21:27:41 Elanor SuSEfirewall2: using default zone 'ext' for interface eth0 Nov 12 21:27:41 Elanor SuSEfirewall2: Firewall rules successfully set Nov 12 21:28:51 Elanor systemd[1]: NetworkManager.service: control process exited, code=exited status=1 Nov 12 21:28:51 Elanor systemd[1]: Job NetworkManager-wait-online.service/start failed with result 'dependency'. Nov 12 21:28:51 Elanor systemd[1]: Unit NetworkManager.service entered failed state. Nov 12 21:28:51 Elanor systemd[1]: dev-sda1.swap swap process exited, code=exited status=255 Nov 12 21:28:51 Elanor systemd[1]: Unit dev-sda1.swap entered failed state. Nov 12 21:29:14 Elanor systemd[1]: NetworkManager.service: control process exited, code=exited status=1 Nov 12 21:29:14 Elanor systemd[1]: Job NetworkManager-wait-online.service/start failed with result 'dependency'. Nov 12 21:29:14 Elanor systemd[1]: Unit NetworkManager.service entered failed state. Nov 12 21:29:14 Elanor systemd[1]: dev-sda1.swap swap process exited, code=exited status=255 Nov 12 21:30:58 Elanor gnome-session[18881]: DEBUG(+): Searching for 6291460 in 6291459,6291460 Nov 12 21:30:58 Elanor gnome-session[18881]: DEBUG(+): Watch 1 fired, idle time = 5 Nov 12 21:30:58 Elanor gnome-session[18881]: DEBUG(+): GsmPresence: setting idle: 0 Nov 12 21:30:58 Elanor gnome-session[18881]: WARNING: Could not connect to ConsoleKit: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name Nov 12 21:31:04 Elanor systemd-logind[18869]: Removed session 44. Nov 12 21:31:04 Elanor avahi-daemon[19318]: avahi-daemon 0.6.30 exiting. Nov 12 20:31:04 Elanor rtkit-daemon[18961]: Exiting cleanly. Nov 12 20:31:04 Elanor rtkit-daemon[18961]: Demoting known real-time threads. Nov 12 20:31:04 Elanor rtkit-daemon[18961]: Successfully demoted thread 18981 of process 18959 (/usr/bin/pulseaudio). Nov 12 20:31:04 Elanor rtkit-daemon[18961]: Demoted 1 threads. Nov 12 20:31:04 Elanor rtkit-daemon[18961]: Exiting watchdog thread. Nov 12 20:31:04 Elanor rtkit-daemon[18961]: Exiting canary thread. Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client1 interface=org.gnome.SessionManager.ClientPrivate method=EndSessionResponse Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: got EndSessionResponse is-ok:1 reason= Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason= Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client4 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason=Client exited in query end session phase instead of end session phase Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: in shutdown, not restarting application Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmStore: Unreffing object: 0x6bfcb0 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client4 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmStore: emitting removed for /org/gnome/SessionManager/Client4 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client4 Nov 12 21:31:04 Elanor gdm-simple-slave[18771]: WARNING: unable to determine if seat can activate sessions: Connection was disconnected before a reply was received Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GdmSignalHandler: handling signal 15 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GdmSignalHandler: Found 1 callbacks Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GdmSignalHandler: running 15 handler: 0x41d2d0 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): Got callback for signal 15 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: Logout called Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): Caught signal 15, shutting down normally. Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GdmSignalHandler: Done handling signals Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:31:04 Elanor rsyslogd: imuxsock: recvfrom UNIX: Resource temporarily unavailable Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmXSMPClient: Client '0x6a6520 [metacity 105e436bd9ccd93cf3132112764418013100000188810002]' received SaveYourselfDone(success = True) Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason= Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: query end session complete Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmShell: Not connected to the shell Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: ending phase QUERY_END_SESSION#012 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: starting phase END_SESSION#012 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: adding client to end-session clients: /org/gnome/SessionManager/Client3 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmXSMPClient: queuing new SaveYourself for '0x6a6520 [metacity 105e436bd9ccd93cf3132112764418013100000188810002]' Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmXSMPClient: Client '0x6a6520 [metacity 105e436bd9ccd93cf3132112764418013100000188810002]' received SaveYourselfDone(success = True) Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: Response from end session request: is-ok=1 do-last=0 cancel=0 reason= Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: ending phase END_SESSION#012 Nov 12 21:31:04 Elanor systemd[1]: systemd-logind.service: main process exited, code=exited, status=1 Nov 12 21:31:04 Elanor systemd[1]: Unit systemd-logind.service entered failed state. Nov 12 21:31:04 Elanor gnome-session[18881]: WARNING: Could not connect to ConsoleKit: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmSessionSave: Clearing saved session Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmSessionSave: clearing currently saved session at /var/lib/gdm/.config/gnome-session/saved-session Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: starting phase EXIT#012 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmXSMPClient: xsmp_stop ('0x6a6520 [metacity 105e436bd9ccd93cf3132112764418013100000188810002]') Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmXsmpServer: ice_io_error_handler (0x7b1520) Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: stopped client: /org/gnome/SessionManager/Client3 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmXSMPClient: IceProcessMessagesIOError on '0x6a6520 [metacity 105e436bd9ccd93cf3132112764418013100000188810002]' Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: disconnect client Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: disconnect client: /org/gnome/SessionManager/Client3 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: in shutdown, not restarting application Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmStore: Unreffing object: 0x6a6520 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client3 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: last client disconnected - exiting Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmManager: ending phase EXIT#012 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client3 Nov 12 21:31:04 Elanor gnome-session[18881]: DEBUG(+): GsmXSMPClient: xsmp_finalize (0x6a6520 [metacity 105e436bd9ccd93cf3132112764418013100000188810002]) Nov 12 21:31:04 Elanor gnome-session[18881]: Gdk-WARNING: The application 'gnome-session' lost its connection to the display :1;#012most likely the X server was shut down or you killed/destroyed#012the application.#012 Nov 12 21:31:06 Elanor kernel: [36238.253106] mtrr: no MTRR for d0000000,2000000 found Nov 12 21:31:28 Elanor dbus[20191]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' Nov 12 21:31:28 Elanor dbus-daemon[20191]: dbus[20191]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' Nov 12 21:31:28 Elanor dbus[20191]: [system] Successfully activated service 'org.freedesktop.login1' Nov 12 21:31:28 Elanor dbus-daemon[20191]: dbus[20191]: [system] Successfully activated service 'org.freedesktop.login1' Nov 12 21:31:28 Elanor systemd-logind[20198]: New seat seat0. Nov 12 21:31:28 Elanor systemd-logind[20198]: New user gdm logged in. Nov 12 21:31:28 Elanor systemd-logind[20198]: New user root logged in. Nov 12 21:31:28 Elanor systemd-logind[20198]: New session 6 of user root. Nov 12 21:31:28 Elanor systemd-logind[20198]: New session 48 of user root. Nov 12 21:31:28 Elanor dbus[20191]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service' Nov 12 21:31:28 Elanor dbus-daemon[20191]: dbus[20191]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service' Nov 12 21:31:28 Elanor console-kit-daemon[20199]: missing action Nov 12 21:31:28 Elanor dbus[20191]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper) Nov 12 21:31:28 Elanor dbus-daemon[20191]: dbus[20191]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper) Nov 12 21:31:28 Elanor polkitd[20266]: started daemon version 0.102 using authority implementation `local' version `0.102' Nov 12 21:31:28 Elanor dbus-daemon[20191]: dbus[20191]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' Nov 12 21:31:28 Elanor dbus[20191]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' Nov 12 21:31:28 Elanor dbus-daemon[20191]: dbus[20191]: [system] Successfully activated service 'org.freedesktop.ConsoleKit' Nov 12 21:31:28 Elanor dbus[20191]: [system] Successfully activated service 'org.freedesktop.ConsoleKit' Nov 12 21:34:13 Elanor avahi-daemon[20331]: Found user 'avahi' (UID 106) and group 'avahi' (GID 106). Nov 12 21:34:13 Elanor avahi-daemon[20331]: Successfully dropped root privileges. Nov 12 21:34:13 Elanor avahi-daemon[20331]: avahi-daemon 0.6.30 starting up. Nov 12 21:34:13 Elanor avahi-daemon[20331]: Loading service file /etc/avahi/services/sftp-ssh.service. Nov 12 21:34:13 Elanor avahi-daemon[20331]: Loading service file /etc/avahi/services/ssh.service. Nov 12 21:34:13 Elanor avahi-daemon[20331]: Loading service file /etc/avahi/services/udisks.service. Nov 12 21:34:13 Elanor avahi-daemon[20331]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.74.131. Nov 12 21:34:13 Elanor systemd[1]: Job NetworkManager-wait-online.service/start failed with result 'dependency'. Nov 12 21:34:13 Elanor systemd[1]: Unit NetworkManager.service entered failed state. Nov 12 21:34:13 Elanor systemd[1]: dev-sda1.swap swap process exited, code=exited status=255 Nov 12 21:34:13 Elanor avahi-daemon[20331]: New relevant interface eth0.IPv4 for mDNS. Nov 12 21:34:13 Elanor avahi-daemon[20331]: Network interface enumeration completed. Nov 12 21:34:13 Elanor avahi-daemon[20331]: Registering new address record for fe80::20c:29ff:fe6b:7077 on eth0.*. Nov 12 21:34:13 Elanor avahi-daemon[20331]: Registering new address record for 192.168.74.131 on eth0.IPv4. Nov 12 21:34:13 Elanor avahi-daemon[20331]: Registering HINFO record with values 'X86_64'/'LINUX'. Nov 12 21:34:13 Elanor systemd-readahead-collect[20328]: Disabling readahead collector due to execution in virtualized environment. Nov 12 21:34:13 Elanor systemd[1]: Unit dev-sda1.swap entered failed state. Nov 12 21:34:13 Elanor xdm[20326]: Starting service gdm..done Nov 12 21:34:14 Elanor avahi-daemon[20331]: Disconnected from D-Bus, exiting. Nov 12 21:34:14 Elanor avahi-daemon[20331]: Got SIGTERM, quitting. Nov 12 21:34:14 Elanor avahi-daemon[20331]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.74.131. Nov 12 21:34:14 Elanor systemd[1]: systemd-logind.service: main process exited, code=exited, status=1 Nov 12 21:34:14 Elanor avahi-daemon[20331]: avahi-daemon 0.6.30 exiting. Nov 12 21:34:14 Elanor systemd[1]: Unit systemd-logind.service entered failed state. Nov 12 21:34:15 Elanor kernel: [36427.004401] mtrr: no MTRR for d0000000,2000000 found Nov 12 21:34:19 Elanor dbus[20392]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service' Nov 12 21:34:19 Elanor dbus-daemon[20392]: dbus[20392]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service' Nov 12 21:34:19 Elanor dbus[20392]: [system] Successfully activated service 'org.freedesktop.Accounts' Nov 12 21:34:19 Elanor dbus-daemon[20392]: dbus[20392]: [system] Successfully activated service 'org.freedesktop.Accounts' Nov 12 21:34:19 Elanor dbus[20392]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper) Nov 12 21:34:19 Elanor dbus-daemon[20392]: dbus[20392]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper) Nov 12 21:34:19 Elanor console-kit-daemon[20415]: missing action Nov 12 21:34:19 Elanor polkitd[20482]: started daemon version 0.102 using authority implementation `local' version `0.102' Nov 12 21:34:19 Elanor dbus-daemon[20392]: dbus[20392]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' Nov 12 21:34:19 Elanor dbus[20392]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' Nov 12 21:34:19 Elanor accounts-daemon[20416]: started daemon version 0.6.15 Nov 12 21:34:19 Elanor dbus-daemon[20392]: dbus[20392]: [system] Successfully activated service 'org.freedesktop.ConsoleKit' Nov 12 21:34:19 Elanor dbus[20392]: [system] Successfully activated service 'org.freedesktop.ConsoleKit' Nov 12 21:34:19 Elanor dbus-daemon[20392]: dbus[20392]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' Nov 12 21:34:19 Elanor dbus[20392]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' Nov 12 21:34:19 Elanor dbus-daemon[20392]: dbus[20392]: [system] Successfully activated service 'org.freedesktop.login1' Nov 12 21:34:19 Elanor dbus[20392]: [system] Successfully activated service 'org.freedesktop.login1' Nov 12 21:34:19 Elanor systemd-logind[20489]: New seat seat0. Nov 12 21:34:19 Elanor systemd-logind[20489]: New user gdm logged in. Nov 12 21:34:19 Elanor systemd-logind[20489]: New user root logged in. Nov 12 21:34:19 Elanor systemd-logind[20489]: New session 48 of user root. Nov 12 21:34:19 Elanor systemd-logind[20489]: New session 6 of user root. Nov 12 21:34:19 Elanor systemd-logind[20489]: New session 49 of user gdm. Nov 12 21:34:19 Elanor systemd-logind[20489]: Linked /tmp/.X11-unix/X1 to /run/user/gdm/X11/display. Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): Enabling debugging Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): GsmShell: Not connected to the shell Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): GdmSignalHandler: Adding handler 4: signum=6 (nil) Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): GdmSignalHandler: Adding handler 8: signum=10 0x41d2d0 Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): fill: *** Looking if /usr/share/gdm/greeter/gnome-session/sessions/gdm-shell.session is a valid session file Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): fill: *** Launching helper '/usr/lib/gnome-session-check-accelerated' to know if session is runnable Nov 12 21:34:19 Elanor gnome-session[20499]: WARNING: Session 'gdm-shell' runnable check failed: Exited with code 1 Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): GsmUtil: Looking for file 'metacity.desktop' Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): GsmUtil: Looking in '/usr/share/gdm/greeter/applications' Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): GsmUtil: Looking in '/usr/share/gnome/autostart' Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): GsmUtil: Looking in '/usr/share/gnome/autostart' Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): fill: *** Done checking required components and providers Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): GsmUtil: Looking in '/etc/xdg/autostart' Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): GsmUtil: Looking in '/var/lib/gdm/.local/share/applications' Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): fill: *** Done adding required components Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): GsmUtil: Looking in '/usr/share/gnome/autostart' Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): GsmManager: read /usr/share/applications/metacity.desktop Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): GsmManager: Phase INITIALIZATION Nov 12 21:34:19 Elanor gnome-session[20499]: DEBUG(+): GsmManager: Phase APPLICATION Nov 12 21:34:19 Elanor dbus-daemon[20392]: dbus[20392]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper) Nov 12 21:34:19 Elanor dbus[20392]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper) Nov 12 21:34:19 Elanor dbus-daemon[20392]: dbus[20392]: [system] Successfully activated service 'org.freedesktop.UPower' Nov 12 21:34:19 Elanor dbus[20392]: [system] Successfully activated service 'org.freedesktop.UPower' Nov 12 21:34:19 Elanor dbus-daemon[20392]: (upowerd:20512): UPower-Linux-WARNING **: failed to open /etc/crypttab: Failed to open file '/etc/crypttab': No such file or directory Nov 12 21:34:19 Elanor kernel: [36431.509298] EXT4-fs (sda2): re-mounted. Opts: acl,user_xattr,commit=0 Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmManager: RegisterClient 1027d8369ae362a0dd132113005953174800000204990001 Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmManager: Adding new client 1027d8369ae362a0dd132113005953174800000204990001 to session Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): uid = 109 Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): pid = 20506 Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmStore: Adding object id /org/gnome/SessionManager/Client1 to store Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmManager: Client added: /org/gnome/SessionManager/Client1 Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): App gnome-settings-daemon.desktop registered Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmManager: ending phase INITIALIZATION#012 Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmManager: starting phase WINDOW_MANAGER#012 Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmManager: starting app '/org/gnome/SessionManager/App3' Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): Starting app: /org/gnome/SessionManager/App3 Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmAutostartApp: starting metacity.desktop: command=metacity startup-id=1027d8369ae362a0dd132113005953261500000204990002 Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmAutostartApp: started pid:20587 Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager interface=org.freedesktop.DBus.Properties method=GetAll Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager interface=org.gnome.SessionManager method=RegisterClient Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmManager: RegisterClient Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmManager: Adding new client 1027d8369ae362a0dd132113006011250200000204990003 to session Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): uid = 109 Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client2 interface=org.freedesktop.DBus.Properties method=GetAll Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager/Client1 interface=org.freedesktop.DBus.Properties method=GetAll Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmXsmpServer: accept_ice_connection() Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmXSMPClient: Initializing client 0x6a6520 [] Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmManager: ending phase DESKTOP#012 Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmPresence: adding idle watch Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmXSMPClient: Set properties from client '0x6a6520 [1027d8369ae362a0dd132113005953261500000204990002]' Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmXSMPClient: Program = 'metacity' Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmXSMPClient: RestartStyleHint = 2 Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmXSMPClient: _GSM_Priority = 20 Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gdm-simple-greeter[20591]: Gtk-WARNING: gtkwidget.c:6857: widget not within a GtkWindow Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): GsmDBusClient: obj_path=/org/gnome/SessionManager interface=org.gnome.SessionManager method=RegisterClient Nov 12 21:34:20 Elanor gnome-session[20499]: DEBUG(+): uid = 109 Nov 12 21:34:23 Elanor systemd[1]: NetworkManager.service: control process exited, code=exited status=1 - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6+2lIACgkQtTMYHG2NR9XfAwCeJ2oeZ9PDMhWaEZe+PBRV23m2 2dwAnjTPZuNWBQGY5ooJP4L7wPxox4vF =uq7a -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday 12 November 2011 21:42:58 Carlos E. R. wrote:
It says swap failed, but swap is active. And by the way, when I tried to log in the graphic session, it died and dumped my in text mode - finally!
It sounds like your problem is with gdm, not with systemd (and believe me, I am not trying to defend systemd, I think it is extra complication for essentially no added benefit, and all it gives us is more chances for bugs) I have noted in the past that gdm sometimes fails to stop even if you stop it with "rcxdm stop". This has happened quite often for me with gdm, through many suse versions. Could you - just for testing - try using kdm instead, and see if "init 3" behaves as it should then? I kind of suspect it will Anders -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2011-11-13 at 02:34 +0100, Anders Johansson wrote:
On Saturday 12 November 2011 21:42:58 Carlos E. R. wrote:
It says swap failed, but swap is active. And by the way, when I tried to log in the graphic session, it died and dumped my in text mode - finally!
It sounds like your problem is with gdm, not with systemd (and believe me, I am not trying to defend systemd, I think it is extra complication for essentially no added benefit, and all it gives us is more chances for bugs)
I have to recogn that the boot speed (till login prompt) is surprisingly fast, compared to init v in the same install. But I don't like what I don't understand. I often edit services or add some, and now I have no idea what to do. Thus I'll probably update using the workaround described in http://en.opensuse.org/openSUSE:Most_annoying_bugs_12.1#Upgrade
I have noted in the past that gdm sometimes fails to stop even if you stop it with "rcxdm stop". This has happened quite often for me with gdm, through many suse versions.
I haven't seen it before.
Could you - just for testing - try using kdm instead, and see if "init 3" behaves as it should then? I kind of suspect it will
Ugh. It is a very small setup inside Vmware Player. Kdm brings a lot of packages... Ok, I'll do it. Now it is 02:56. It will take time to download. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6/JcAACgkQtTMYHG2NR9V0sACePlg3dAMydbyyrOT8UyJhtHOG u5IAoJlSELjVtTSnXyOkcstFgsW/dC1f =Imhx -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2011-11-13 at 03:04 +0100, Carlos E. R. wrote:
Could you - just for testing - try using kdm instead, and see if "init 3" behaves as it should then? I kind of suspect it will
Ugh. It is a very small setup inside Vmware Player. Kdm brings a lot of packages... Ok, I'll do it.
Now it is 02:56. It will take time to download.
Almost 400MB compressed. Now it is 3:49. But you were right, with KDM it works. I tried a dozen times. Now, to remove all those things I installed. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6/MKwACgkQtTMYHG2NR9VHRACfSYjkn/2Yr7X67kdReir9AAtf w4YAnjl8xKfJZdQY+NPMB0f1YQDe/QtA =MBKf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 13 November 2011 03:51:23 Carlos E. R. wrote:
On Sunday, 2011-11-13 at 03:04 +0100, Carlos E. R. wrote:
Could you - just for testing - try using kdm instead, and see if "init 3" behaves as it should then? I kind of suspect it will
Ugh. It is a very small setup inside Vmware Player. Kdm brings a lot of packages... Ok, I'll do it.
Now it is 02:56. It will take time to download.
Almost 400MB compressed. Now it is 3:49. But you were right, with KDM it works. I tried a dozen times.
That's good to hear. That means it's a bug in gdm, which doesn't surprise me. As for understanding systemd, I don't understand it at all. I've spent the past few hours trying to understand how the display manager is launched in the first place, and I haven't been able to find anything. I know this much: /etc/init.d/rc is still being used, so the runlevels are still started the old fashioned way, at least for most things, and kdm is started through the standard /etc/init.d/xdm script. What I don't know: where rc is run from. I cannot find this, or any reference to it or inittab anywhere in the systemd source code, or in any of the configuration files. It should mean though that your old way of adding services will still work I have also seen that systemd runs everything in parallel, and there is no apparent way of disabling that, which worries me a little, since RUN_PARALLEL=yes is the source of many problems and setting it to no is a very frequent solution (or at least workaround). If this is no longer available, I wonder what will happen. Anders -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2011-11-13 at 04:30 +0100, Anders Johansson wrote:
On Sunday 13 November 2011 03:51:23 Carlos E. R. wrote:
That's good to hear. That means it's a bug in gdm, which doesn't surprise me.
I'll fill the bugzilla tomorrow, but against what, gnome? Now it is 4:34 AM, I should be in bed.
As for understanding systemd, I don't understand it at all. I've spent the past few hours trying to understand how the display manager is launched in the first place, and I haven't been able to find anything.
I think we have an hybrid, initd - systemd.
I know this much: /etc/init.d/rc is still being used, so the runlevels are still started the old fashioned way, at least for most things, and kdm is started through the standard /etc/init.d/xdm script.
I read somewhere that services were not all migrated to the new system. That if the equivalent exist, it is used, if not, the old one. Don't know how.
What I don't know: where rc is run from. I cannot find this, or any reference to it or inittab anywhere in the systemd source code, or in any of the configuration files.
It should mean though that your old way of adding services will still work
Via insserv?
I have also seen that systemd runs everything in parallel, and there is no apparent way of disabling that, which worries me a little, since RUN_PARALLEL=yes is the source of many problems and setting it to no is a very frequent solution (or at least workaround). If this is no longer available, I wonder what will happen.
They fail with initd, perhaps not with systemd. But this systemd works silently, doesn't output text to the first console, we don't see if things worked or failed, or if it is stalling at some point. Just now I booted my 12.1 test system, level 5. I logged in, then tried to also log in via ssh from the host system. But it was not responding! It boots so fast because it is delaying the startup of other services. I had to wait about a minute. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6/PK0ACgkQtTMYHG2NR9VDdACfTjOA1lralI2ApZ+lMKM9PpJX kEQAoIARVHWNYnLRqexNEr8eqwWKBdYU =IanW -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 13 November 2011 04:42:37 Carlos E. R. wrote:
I know this much: /etc/init.d/rc is still being used, so the runlevels are still started the old fashioned way, at least for most things, and kdm is started through the standard /etc/init.d/xdm script.
I read somewhere that services were not all migrated to the new system. That if the equivalent exist, it is used, if not, the old one. Don't know how.
Yes, that is documented in the man page. If a "target" requests foo.service, and this doesn't exist, it will try to start /etc/init.d/rc This isn't what I'm talking about. I'm talking about the boot process running /etc/init.d/rc <runlevel> on boot. In /var/log/boot.msg you can see the log messages from "Master Resource Control" which come from this script. But I haven't been able to find any place where this gets run. I've greped myself bloody in the source code and in the configuration files, and I still cannot find this
What I don't know: where rc is run from. I cannot find this, or any reference to it or inittab anywhere in the systemd source code, or in any of the configuration files.
It should mean though that your old way of adding services will still work Via insserv?
Looks like it's still working, yes
I have also seen that systemd runs everything in parallel, and there is no apparent way of disabling that, which worries me a little, since RUN_PARALLEL=yes is the source of many problems and setting it to no is a very frequent solution (or at least workaround). If this is no longer available, I wonder what will happen.
They fail with initd, perhaps not with systemd.
Perhaps. What worries me is that the quickie fix/workaround appears to no longer be there if they do fail But RUN_PARALLEL is interpreted by /etc/init.d/rc so maybe it will still work after all. I'm just worried that the future plan is to migrate away from this to a "pure" systemd setup, and then it will be really gone Anders -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/12/2011 10:42 PM, Carlos E. R. pecked at the keyboard and wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sunday, 2011-11-13 at 04:30 +0100, Anders Johansson wrote:
On Sunday 13 November 2011 03:51:23 Carlos E. R. wrote:
That's good to hear. That means it's a bug in gdm, which doesn't surprise me.
I'll fill the bugzilla tomorrow, but against what, gnome? Now it is 4:34 AM, I should be in bed.
As for understanding systemd, I don't understand it at all. I've spent the past few hours trying to understand how the display manager is launched in the first place, and I haven't been able to find anything.
I think we have an hybrid, initd - systemd.
I know this much: /etc/init.d/rc is still being used, so the runlevels are still started the old fashioned way, at least for most things, and kdm is started through the standard /etc/init.d/xdm script.
I read somewhere that services were not all migrated to the new system. That if the equivalent exist, it is used, if not, the old one. Don't know how.
What I don't know: where rc is run from. I cannot find this, or any reference to it or inittab anywhere in the systemd source code, or in any of the configuration files.
It should mean though that your old way of adding services will still work
Via insserv?
I have also seen that systemd runs everything in parallel, and there is no apparent way of disabling that, which worries me a little, since RUN_PARALLEL=yes is the source of many problems and setting it to no is a very frequent solution (or at least workaround). If this is no longer available, I wonder what will happen.
They fail with initd, perhaps not with systemd.
But this systemd works silently, doesn't output text to the first console, we don't see if things worked or failed, or if it is stalling at some point.
Just now I booted my 12.1 test system, level 5. I logged in, then tried to also log in via ssh from the host system. But it was not responding! It boots so fast because it is delaying the startup of other services. I had to wait about a minute.
My experience is that the system isn't booting any faster, it's just starting "X" sooner so it *appears* to boot faster. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2011-11-12 at 23:00 -0500, Ken Schneider - openSUSE wrote:
My experience is that the system isn't booting any faster, it's just starting "X" sooner so it *appears* to boot faster.
I think you are right. And the appeareance is helped by not printing messages to tty1. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6/uIUACgkQtTMYHG2NR9U9CQCfZNXvgy9vDRlpblkVa40cJn6p T88An3PGvfHcMbClibyTq46pld4ZDs5L =j2oR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Ken Schneider - openSUSE wrote:
My experience is that the system isn't booting any faster, it's just starting "X" sooner so it *appears* to boot faster.
Yep. With earlier versions, I could click on something as soon as I could see it and expect it to run. Not any more, just like Windows. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le 13/11/2011 13:52, James Knott a écrit :
Ken Schneider - openSUSE wrote:
My experience is that the system isn't booting any faster, it's just starting "X" sooner so it *appears* to boot faster.
Yep. With earlier versions, I could click on something as soon as I could see it and expect it to run. Not any more, just like Windows.
well... it runs as fast as the slower service (usually dhcp), it simply parallelize them as much as possible jdd -- http://www.dodin.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2011-11-13 at 04:42 +0100, Carlos E. R. wrote:
On Sunday, 2011-11-13 at 04:30 +0100, Anders Johansson wrote:
That's good to hear. That means it's a bug in gdm, which doesn't surprise me.
I'll fill the bugzilla tomorrow, but against what, gnome? Now it is 4:34 AM, I should be in bed.
Bug 730051 - "init 3" doesn't work with systemd and gdm - 12.1 RC2 - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6/0CsACgkQtTMYHG2NR9XK6QCfQojbhySMOIn5UJzaU9ZfU69O JxoAn385Ytp68b4k/qgx0G6emRdPNr+d =nenp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 13 November 2011, Anders Johansson wrote:
On Sunday 13 November 2011 03:51:23 Carlos E. R. wrote:
On Sunday, 2011-11-13 at 03:04 +0100, Carlos E. R. wrote:
Could you - just for testing - try using kdm instead, and see if "init 3" behaves as it should then? I kind of suspect it will
Ugh. It is a very small setup inside Vmware Player. Kdm brings a lot of packages... Ok, I'll do it.
Now it is 02:56. It will take time to download.
Almost 400MB compressed. Now it is 3:49. But you were right, with KDM it works. I tried a dozen times.
That's good to hear. That means it's a bug in gdm, which doesn't surprise me.
Systemd claims to have special gnome support. Probably it's a feature that init 3 don't stop it.
As for understanding systemd, I don't understand it at all. I've spent the past few hours trying to understand how the display manager is launched in the first place, and I haven't been able to find anything.
That's a feature too. The usual user don't want to understand it so nobody should understand it.
I know this much: /etc/init.d/rc is still being used, so the runlevels are still started the old fashioned way, at least for most things, and kdm is started through the standard /etc/init.d/xdm script.
What I don't know: where rc is run from. I cannot find this, or any reference to it or inittab anywhere in the systemd source code, or in any of the configuration files.
IMO it's a shame that experienced *nix users need to reverse engineer such simple tasks. Systemd is broken by design.
It should mean though that your old way of adding services will still work
I have also seen that systemd runs everything in parallel, and there is no apparent way of disabling that, which worries me a little, since RUN_PARALLEL=yes is the source of many problems and setting it to no is a very frequent solution (or at least workaround). If this is no longer available, I wonder what will happen.
Yup, patching startpar into sysvinit was also a huge mistake. cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2011-11-13 at 05:26 +0100, Rüdiger Meier wrote:
On Sunday 13 November 2011, Anders Johansson wrote:
That's good to hear. That means it's a bug in gdm, which doesn't surprise me.
Systemd claims to have special gnome support. Probably it's a feature that init 3 don't stop it.
When I do init 3, gdm doesn't die. But the moment I enter the password it dies, leaving me in text mode.
IMO it's a shame that experienced *nix users need to reverse engineer such simple tasks. Systemd is broken by design.
Indeed it is a shame. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6/uScACgkQtTMYHG2NR9XRrQCeMJrgoxlqymipXtrR3GZZlYDi 13YAn36u8L3bhxeDWzNUidaUcl88p8O5 =WkYU -----END PGP SIGNATURE-----
Carlos E. R. wrote:
On Sunday, 2011-11-13 at 05:26 +0100, Rüdiger Meier wrote:
On Sunday 13 November 2011, Anders Johansson wrote:
That's good to hear. That means it's a bug in gdm, which doesn't surprise me.
Systemd claims to have special gnome support. Probably it's a feature that init 3 don't stop it.
When I do init 3, gdm doesn't die. But the moment I enter the password it dies, leaving me in text mode.
IMO it's a shame that experienced *nix users need to reverse engineer such simple tasks. Systemd is broken by design.
Indeed it is a shame.
Nah, systemd brings lots of useful features - you guys are just being reactionary and opposed to progress. :-) -- Per Jessen, Zürich (6.8°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2011-11-13 at 18:52 +0100, Per Jessen wrote:
Nah, systemd brings lots of useful features - you guys are just being reactionary and opposed to progress. :-)
When it gets properly documented. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk7ACfsACgkQtTMYHG2NR9Ud3ACeI/9VfBaAQ1R5Rbd3tVGmdqzq jPkAnidMAptqF9z+D4ajOMsRPijGu+Up =W/pe -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Ne 13. November 2011, 18:52:18 CET, Per Jessen wrote:
Nah, systemd brings lots of useful features - you guys are just being reactionary and opposed to progress. :-)
No, I'm certainly not opposed to progress as such. But the progress must bring something positive. I welcomed udev, I've been using iproute2 since the days most Linux users didn't know it existed (well, maybe most don't even today but that's another story). On the other hand, I criticized zmd in 10.1, I criticized having KDE4 as default when it was far from ready and I do criticize having systemd now because it is about as ready as KDE4 was when it first appeared in OpenSuSE. It is buggy, it is poorly documented, configuration is much more complicated, it makes diagnostic of the boot process harder. What does it give me? A bit faster boot (or maybe only makes it look faster). I'm sorry, I can't see this as a good deal. And unlike with KDE4, most of the problems are not going to disappear. Bugs will be fixed eventually, documentation is going to be written but complicated configuration, complicated diagnostic and incompatibility with third party projets will stay. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 13 November 2011 23:12:58 Michal Kubecek wrote:
On Ne 13. November 2011, 18:52:18 CET, Per Jessen wrote:
Nah, systemd brings lots of useful features - you guys are just being reactionary and opposed to progress. :-)
No, I'm certainly not opposed to progress as such. But the progress must bring something positive. I welcomed udev, I've been using iproute2 since the days most Linux users didn't know it existed (well, maybe most don't even today but that's another story).
On the other hand, I criticized zmd in 10.1, I criticized having KDE4 as default when it was far from ready and I do criticize having systemd now because it is about as ready as KDE4 was when it first appeared in OpenSuSE.
I was in favour of KDE4 (and still am) because it did bring features. Even though it was buggy, there was something there. It was obvious that when it matured, it would become something new that we didn't have before I cannot say the same for systemd. Even giving it all the benefits of every single doubt in the world, I cannot see that it brings us anything we didn't have before, except a fresh new load of headache. It is simply wasted development cycles that could have been better spent on other things, because even when systemd is working exactly according to specs, we will have exactly nothing that we didn't have before. No new functionality at all Anders -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Anders Johansson wrote:
On Sunday 13 November 2011 23:12:58 Michal Kubecek wrote:
On Ne 13. November 2011, 18:52:18 CET, Per Jessen wrote:
Nah, systemd brings lots of useful features - you guys are just being reactionary and opposed to progress. :-)
No, I'm certainly not opposed to progress as such. But the progress must bring something positive. I welcomed udev, I've been using iproute2 since the days most Linux users didn't know it existed (well, maybe most don't even today but that's another story).
On the other hand, I criticized zmd in 10.1, I criticized having KDE4 as default when it was far from ready and I do criticize having systemd now because it is about as ready as KDE4 was when it first appeared in OpenSuSE.
I was in favour of KDE4 (and still am) because it did bring features. Even though it was buggy, there was something there. It was obvious that when it matured, it would become something new that we didn't have before
I cannot say the same for systemd. Even giving it all the benefits of every single doubt in the world, I cannot see that it brings us anything we didn't have before, except a fresh new load of headache. It is simply wasted development cycles that could have been better spent on other things, because even when systemd is working exactly according to specs, we will have exactly nothing that we didn't have before. No new functionality at all
Agree completely, I see that my attempted humour was a complete flop. -- Per Jessen, Zürich (4.4°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 13 November 2011, Michal Kubecek wrote:
On the other hand, I criticized zmd in 10.1, I criticized having KDE4 as default when it was far from ready and I do criticize having systemd now because it is about as ready as KDE4 was when it first appeared in OpenSuSE.
The thing is that zmd, kde4 or other mistakes were easily to ignore but the systemd thing is even worse seeing all these patches and dependencies against formerly stable packages.
It is buggy, it is poorly documented, configuration is much more complicated, it makes diagnostic of the boot process harder.What does it give me? A bit faster boot (or maybe only makes it look faster).
Yup, personally I have no use case where boot time matters. The time I need to fix a non booting system matters. And that's why I want to stick with init shell scripts instead of systemd binary black box even if systemd would be stable. cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/13/2011 5:12 PM, Michal Kubecek wrote:
On Ne 13. November 2011, 18:52:18 CET, Per Jessen wrote:
Nah, systemd brings lots of useful features - you guys are just being reactionary and opposed to progress. :-)
No, I'm certainly not opposed to progress as such. But the progress must bring something positive. I welcomed udev, I've been using iproute2 since the days most Linux users didn't know it existed (well, maybe most don't even today but that's another story).
On the other hand, I criticized zmd in 10.1, I criticized having KDE4 as default when it was far from ready and I do criticize having systemd now because it is about as ready as KDE4 was when it first appeared in OpenSuSE. It is buggy, it is poorly documented, configuration is much more complicated, it makes diagnostic of the boot process harder. What does it give me? A bit faster boot (or maybe only makes it look faster). I'm sorry, I can't see this as a good deal. And unlike with KDE4, most of the problems are not going to disappear. Bugs will be fixed eventually, documentation is going to be written but complicated configuration, complicated diagnostic and incompatibility with third party projets will stay.
I'm sure the systemd home page will provide a full summary of it's goals. Without even having looked at their home page I already know it makes it possible to express lots more accurate and dynamic start/stop dependencies and procedures for subsystems. Don't be like what Ford said about what users want. If he had asked people what they wanted they wouldn't have said motor cars, they'd have said faster horses. Cars are a huge downgrade from horses in many ways. They don't reproduce themselves, they can't drive themselves safely with you asleep or drunk, or missing altogether. They can't climb mountain trails and jump fenses. They don't come to you automatically when you whistle. You get speeding tickets in them but never on a horse. You don't have to dig horse fuel out of the ground on the other side of the planet and protect it with wars and then boil it in huge stills and then be super careful not to let it catch fire or explode the whole time it's being stored and used. You can't get a speeding ticket on a horse. Horses don't need paved roads and toxic substances in general. Dead horses enrich the environment. Dead cars accumulate in huge ugly toxic junk yards. All your saddles and horseshoes and stables are incompatible. Also all the poor people with jobs in any of the related support industries. I agree, it, and opensuse's implementation of it, has issues still. That's just a reason to delay using it outside of testing and development, not a reason to consider it a bad goal altogether. -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 14 of November 2011, Brian K. White wrote:
On 11/13/2011 5:12 PM, Michal Kubecek wrote: I'm sure the systemd home page will provide a full summary of it's goals.
I've read it. I read several articles about it. When you look through the big words and phrases, there is nothing. Nothing else than (maybe) a bit faster boot which is payed for by great complexity (leading to more complicated configuration and diagnostic) and incompatibility with third-party projects; some of them not developed primarily for Linux and some not developed with Linux in mind at all; their developers are not going to automatically accept the "the way you've been doing it until now is wrong, rewrite your daemons not to be daemons".
Without even having looked at their home page I already know it makes it possible to express lots more accurate and dynamic start/stop dependencies and procedures for subsystems.
Nice example of those phrases I mentioned above. What does this "dynamic" really mean? On one hand, unnecessary complexity, complicated configuration, difficulties with diagnostic. On the other hand, maybe few seconds of boot time. On some computers, I boot once a day (twice if there is a kernel update), on others every two weeks, on some every two or three months. On none of them, few seconds of boot time matter.
Don't be like what Ford said about what users want. If he had asked people what they wanted they wouldn't have said motor cars, they'd have said faster horses.
Cars had issues but they had potential. This is in fact analogy of KDE4 - it was in very bad shape when it appeared but it was clear from the beginning that it will be better than KDE3 one day (and I never said KDE4 was bad as such - I ony criticized that it was made default too early and that KDE3 was removed too early). With systemd, this is not the case. It tries to solve an artificially overrated problem and does more harm than good. Even if the problems with documentation and bugs are solved one day, the rest is to stay. And these intrinsic problems are enough to outweight the few seconds of boot time you get. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 13 November 2011 21:57:40 Brian K. White wrote:
Without even having looked at their home page I already know it makes it possible to express lots more accurate and dynamic start/stop dependencies and procedures for subsystems.
Does it? In what way, specifically? How is "wants" and "requires" more accurate or dynamic than "should-start" or "required-start". I am curious. And I have still not been able to find where the damn thing launches /etc/init.d/rc I see absolutely, literally no new functionality in systemd that we did not have before. This includes parallelized booting. Feel free to name examples Anders -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
(will be interesting if this mail gets past the censor) On 14.11.2011 08:37, Anders Johansson wrote:
I see absolutely, literally no new functionality in systemd that we did not have before. This includes parallelized booting. Feel free to name examples
puts each service into its own cgroup => reliable stopping of services My customers will love to see this in SLES. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 14 of November 2011, Stefan Seyfried wrote:
On 14.11.2011 08:37, Anders Johansson wrote:
I see absolutely, literally no new functionality in systemd that we did not have before. This includes parallelized booting. Feel free to name examples
puts each service into its own cgroup => reliable stopping of services
Are you sure this is not possible with traditional init scripts? I can't see a reason why it wouldn't.
My customers will love to see this in SLES.
Actually, the idea of having systemd in SLES is what really frightens me. If the experience with systemd in OpenSuSE 12.1 helps to prevent that, there might be some good from it after all. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 14.11.2011 09:55, Michal Kubeček wrote:
On Monday 14 of November 2011, Stefan Seyfried wrote:
On 14.11.2011 08:37, Anders Johansson wrote:
I see absolutely, literally no new functionality in systemd that we did not have before. This includes parallelized booting. Feel free to name examples
puts each service into its own cgroup => reliable stopping of services
Are you sure this is not possible with traditional init scripts? I can't see a reason why it wouldn't.
You would need to touch each and every init script. While systemd happily continues to run old-stye init scripts. I forgot a few more benefits: * lossless loging from the beginning * easy display of system state (stuff like systemctl list-units --failed - do this with sysv init!) On real work systems, nobody cares what's printed on the console - simply because there is no console attached. But people care how to find out if startup worked. And they care for logs. My customers will love to see this in SLES, too. I was also suspicious of the change at first. You know, as an old fart, you don't like learning new stunts. But the actually working code convinced me. Of course there is the occasional glitch. But hell - I have had more problems with sysvinit in the last year than I had with systemd and that even though I'm running it since its very first incantation in Factory. (Sys V init mysteriously (and no way to find out why!) not starting single init scripts even though the S* and K* links were there is just one example). So instead of complaining I decided to simply fix the stuff that's still causing troubles. But for now it is just working fine for me and I will have to find something to fix. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Stefan Seyfried wrote:
I forgot a few more benefits:
* lossless loging from the beginning * easy display of system state (stuff like systemctl list-units --failed - do this with sysv init!) On real work systems, nobody cares what's printed on the console - simply because there is no console attached. But people care how to find out if startup worked. And they care for logs.
When you're installing or debugging a start-up issue on a production system, the console log (direct/serial/ipmi) is very useful though. -- Per Jessen, Zürich (5.3°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 14.11.2011 10:34, Per Jessen wrote:
When you're installing or debugging a start-up issue on a production
system, the console log (direct/serial/ipmi) is very useful though.
Yes, of course. And you can still get that with systemd if you want. It will still be much better logged to syslog with systemd than it ever was with sysvinit (ever looked into those /var/log/boot.* files? Ugh!) -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 14 November 2011 10:51:56 Stefan Seyfried wrote:
(ever looked into those /var/log/boot.* files? Ugh!)
I work with those daily, I think they are very useful, if somewhat hard to read. But the solution to the problem "init logs poorly" is not "rewrite everything from the ground up" Anders -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 14 of November 2011, Stefan Seyfried wrote:
You would need to touch each and every init script.
I don't think so. A simple change to /etc/init.d/rc (and /etc/init.d/boot if you want the same for boot.* scripts) would be enough.
I forgot a few more benefits:
* lossless loging from the beginning * easy display of system state (stuff like systemctl list-units --failed - do this with sysv init!) On real work systems, nobody cares what's printed on the console - simply because there is no console attached. But people care how to find out if startup worked. And they care for logs.
Again, these things either are already done for traditional init scripts or can be done easily.
(Sys V init mysteriously (and no way to find out why!) not starting single init scripts even though the S* and K* links were there is just one example).
This is a nice example of problems that are easy to debug with traditional init scripts but much harder with systemd.
So instead of complaining I decided to simply fix the stuff that's still causing troubles. But for now it is just working fine for me and I will have to find something to fix.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 14.11.2011 11:10, Michal Kubeček wrote:
On Monday 14 of November 2011, Stefan Seyfried wrote:
You would need to touch each and every init script.
This was the expression used by the libcgroup developer, I assumed it to be true.
I don't think so. A simple change to /etc/init.d/rc (and /etc/init.d/boot if you want the same for boot.* scripts) would be enough.
Well, nobody did it. With systemd it's there now.
I forgot a few more benefits:
* lossless loging from the beginning * easy display of system state (stuff like systemctl list-units --failed - do this with sysv init!) On real work systems, nobody cares what's printed on the console - simply because there is no console attached. But people care how to find out if startup worked. And they care for logs.
Again, these things either are already done for traditional init scripts or can be done easily.
Hm, unfortunately nobody has done them for 30 years. And the lossless logging will be really hard, I think. Simply because of the socket activation / buffering stuff in systemd.
(Sys V init mysteriously (and no way to find out why!) not starting single init scripts even though the S* and K* links were there is just one example).
This is a nice example of problems that are easy to debug with traditional init scripts but much harder with systemd.
No. It was actually impossible to find the cause. In the end we did something equivalent to (pseudo code) chkconfig --list > tmpfile for i in *; do chkconfig $i off; done $enable_everything_that_was enabled_before < tmpfile After that it mysteriously started working again, even though the links were the same as before. I'm not saying "we will not be seeing strange things in systemd". I'm just thinking that the debugging possibilities are at least as good in systemd than in oldskool init. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 14 November 2011, Stefan Seyfried wrote:
On 14.11.2011 11:10, Michal Kubeček wrote:
This is a nice example of problems that are easy to debug with traditional init scripts but much harder with systemd.
No. It was actually impossible to find the cause. In the end we did something equivalent to (pseudo code)
chkconfig --list > tmpfile for i in *; do chkconfig $i off; done $enable_everything_that_was enabled_before < tmpfile
After that it mysteriously started working again, even though the links were the same as before.
You are joking!? Are you 100% sure that the links were the same as before. So you are telling us that something like this fixed your problem. cp -r /etc/init.d /tmp rm -rf /etc/init.d mv /tmp/init.d /etc If this was the case then I would say you've had some serious issues on that machine beyond any init system. cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 14.11.2011 12:37, Ruediger Meier wrote:
You are joking!? Are you 100% sure that the links were the same as before.
Yes. A find|xargs ls -l.... showed that the only difference was the time of the links. The name and the targets were the same. We had a lengthy debugging session on this and were almost going to file a Service Request. But then we "solved" it with the "recreate all links" voodoo.
So you are telling us that something like this fixed your problem. cp -r /etc/init.d /tmp rm -rf /etc/init.d mv /tmp/init.d /etc
No, we did remove only the links and recreate them, all with insserv/chkconfig.
If this was the case then I would say you've had some serious issues on that machine beyond any init system.
There are thousands of those images deployed here and one showed that issue. Nothing else was bugged. It was a bug. Period. Bugs exist also in SysV init. And it was impossible for us to debug. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 14 November 2011 10:27:48 Stefan Seyfried wrote:
* lossless loging from the beginning
What does this have to do with systemd? It is not a kernel module. Logging from the beginning is a kernel feature (and one that suse has had since anno dazumal)
* easy display of system state (stuff like systemctl list-units --failed - do this with sysv init!) On real work systems, nobody cares what's printed on the console - simply because there is no console attached. But people care how to find out if startup worked. And they care for logs.
/var/log/boot.msg has had this for centuries on suse systems Anything else? Anders -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 14 November 2011 08:59:48 Stefan Seyfried wrote:
(will be interesting if this mail gets past the censor)
I see absolutely, literally no new functionality in systemd that we did not have before. This includes parallelized booting. Feel free to name examples
On 14.11.2011 08:37, Anders Johansson wrote: puts each service into its own cgroup
Hardly necessary to rewrite the entire core infrastructure to achieve
=> reliable stopping of services
heh. No (see the start of this thread, the cause being that systemd was unable to stop gdm). Also, what do you imagine systemd is? It is not a kernel service. It has to work with kill or killproc just like any other tool. If sysvinit fails, so will systemd - or reversed, if the systemd scripts manage to stop a service, then the sysvinit can use the exact same technique to stop it. Again, no need to rewrite the entire infrastructure. Anders -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Anders, On 14.11.2011 13:06, Anders Johansson wrote:
On Monday 14 November 2011 08:59:48 Stefan Seyfried wrote:
(will be interesting if this mail gets past the censor)
puts each service into its own cgroup
Hardly necessary to rewrite the entire core infrastructure to achieve
Well, you can of course rewrite sysv init to do that. Unfortunately, nobody did. Or fix each and every init script. Unfortunately, nobody did. systemd is giving me that for free.
=> reliable stopping of services
heh. No (see the start of this thread, the cause being that systemd was unable to stop gdm).
I'm pretty sure that systemd would be able to stop it, but due to some bug it did not even try to. A bug. Exists in software.
Also, what do you imagine systemd is? It is not a kernel service. It has to work with kill or killproc just like any other tool.
No, it doesn't need killproc, see below. That's maybe one of its biggest advantages.
If sysvinit fails, so will systemd - or reversed, if the systemd scripts manage to stop a service,
Imagine an apache server. A malicious CGI. Double forking. Reparented to init. How do you find out you need to stop the CGI when stopping apache? With systemd it's easy: everything that's in apaches cgroup gets killed. That's not a feature of systemd. To put every service into its own cgroup is a feature of systemd, which just as a side effect brings the
then the sysvinit can use the exact same technique to stop it. Again, no need to rewrite the entire infrastructure.
Of course. Just implement proper cgroups support in sysv init. Nobody did. My customers will like systemd alone for those reasons. Better get accustomed to the thought now :-) -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 14/11/11 02:57, Brian K. White wrote:
On 11/13/2011 5:12 PM, Michal Kubecek wrote:
On Ne 13. November 2011, 18:52:18 CET, Per Jessen wrote:
Nah, systemd brings lots of useful features - you guys are just being reactionary and opposed to progress. :-)
No, I'm certainly not opposed to progress as such. But the progress must bring something positive. I welcomed udev, I've been using iproute2 since the days most Linux users didn't know it existed (well, maybe most don't even today but that's another story).
On the other hand, I criticized zmd in 10.1, I criticized having KDE4 as default when it was far from ready and I do criticize having systemd now because it is about as ready as KDE4 was when it first appeared in OpenSuSE. It is buggy, it is poorly documented, configuration is much more complicated, it makes diagnostic of the boot process harder. What does it give me? A bit faster boot (or maybe only makes it look faster). I'm sorry, I can't see this as a good deal. And unlike with KDE4, most of the problems are not going to disappear. Bugs will be fixed eventually, documentation is going to be written but complicated configuration, complicated diagnostic and incompatibility with third party projets will stay.
I'm sure the systemd home page will provide a full summary of it's goals.
Without even having looked at their home page I already know it makes it possible to express lots more accurate and dynamic start/stop dependencies and procedures for subsystems.
Don't be like what Ford said about what users want. If he had asked people what they wanted they wouldn't have said motor cars, they'd have said faster horses.
Cars are a huge downgrade from horses in many ways. They don't reproduce themselves, they can't drive themselves safely with you asleep or drunk, or missing altogether. They can't climb mountain trails and jump fenses. They don't come to you automatically when you whistle. You get speeding tickets in them but never on a horse. You don't have to dig horse fuel out of the ground on the other side of the planet and protect it with wars and then boil it in huge stills and then be super careful not to let it catch fire or explode the whole time it's being stored and used. You can't get a speeding ticket on a horse. Horses don't need paved roads and toxic substances in general. Dead horses enrich the environment. Dead cars accumulate in huge ugly toxic junk yards. All your saddles and horseshoes and stables are incompatible. Also all the poor people with jobs in any of the related support industries.
I agree, it, and opensuse's implementation of it, has issues still. That's just a reason to delay using it outside of testing and development, not a reason to consider it a bad goal altogether.
Brilliant, this is even better than the one I wrote to a guy some weeks ago. Newton's laws of motion - proven time and time again. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot, Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2011-11-12 at 19:32 +0100, Anders Johansson wrote:
seems to me that "init 3" works now just as well as it did before
No, it doesn't. Elanor:~ # init 3 Elanor:~ # and nothing happens, graphics mode remains active. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6+0HgACgkQtTMYHG2NR9XgcgCfYS0qxFxTReD+qjfgQF6o5QE3 k94An0egy8d9JvsiT5sk1Zx/7Leptkhv =uWP9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12.11.2011 22:00, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Saturday, 2011-11-12 at 19:32 +0100, Anders Johansson wrote:
seems to me that "init 3" works now just as well as it did before
No, it doesn't.
Elanor:~ # init 3 Elanor:~ #
and nothing happens, graphics mode remains active.
Here I can issue init 3 both in virtual console (Alt+Ctrl+F1) or a terminal in GUI. Both work. Then init 5 brings back GUI login. Vahis -- http://waxborg.servepics.com openSUSE 11.4 (x86_64) 2.6.37.6-0.9-default main host openSUSE 12.1 (x86_64) 3.1.0-1.2-desktop in VirtualBox openSUSE 11.4 (i586) 3.1.0-46-desktop "Tumbleweed" in EeePC 900 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On So 12. listopad 2011, 19:32:30 CET, Anders Johansson wrote:
seems to me that "init 3" works now just as well as it did before
It probably does if you have the right init. How about the situation when /sbin/init is a link to systemctl and normal init (from sysvinit) is running (or vice versa)? Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 13 November 2011 22:46:54 Michal Kubecek wrote:
On So 12. listopad 2011, 19:32:30 CET, Anders Johansson wrote:
seems to me that "init 3" works now just as well as it did before
It probably does if you have the right init. How about the situation when /sbin/init is a link to systemctl and normal init (from sysvinit) is running (or vice versa)?
Yes Michal, that was the topic of conversation in this thread. I have it set to systemd, as the output of "rcxdm status" that I pasted in the email you replied to showed. (See where it says "redirecting to systemctl"? It doesn't do that if it isn't using systemd, see /etc/rc.status) Anders -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 13 November 2011 22:46:54 Michal Kubecek wrote:
On So 12. listopad 2011, 19:32:30 CET, Anders Johansson wrote:
seems to me that "init 3" works now just as well as it did before
It probably does if you have the right init. How about the situation when /sbin/init is a link to systemctl and normal init (from sysvinit) is running (or vice versa)?
Oh, sorry, I misread your email. I doubt very much that this is a supported scenario. The man page for systemd seems to suggest that it will work, but I am almost positive that sysvinit won't know about systemd. Anders -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12.11.2011 16:42, Richard Brown wrote:
Okay, maybe I'm missing something in this long debate..but, what exactly is the problem here?
systemctl doesn't have the same concept of runlevels as sysvinit
init 3 used to be a convenient way of booting a system that had X installed without loading X
I seem to be missing something here, too. I can still use init 3 and init 5, just like before.
systemctl disable xdm.service is arguably just as easy a way of accomplishing the same thing with systemd, with systemctl start xdm.service being how you'd start X when you want it, systemctl stop xdm.service being how to stop it when you're done with it..
I can do this, too.
Am I missing something here?
Apparently at least I am. Vahis -- http://waxborg.servepics.com openSUSE 11.4 (x86_64) 2.6.37.6-0.9-default main host openSUSE 12.1 (x86_64) 3.1.0-1.2-desktop in VirtualBox openSUSE 11.4 (i586) 3.1.0-46-desktop "Tumbleweed" in EeePC 900 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2011-11-12 at 20:21 +0200, Vahis wrote:
I seem to be missing something here, too. I can still use init 3 and init 5, just like before.
I can't. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk6+0aIACgkQtTMYHG2NR9WcMQCghoJucNxhVL6L0JaXtmgG260L NXcAn3RcMJ5eNsYt+K4kA9zpfzLx957D =/NNq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (19)
-
Anders Johansson
-
Anders Johansson
-
Brian K. White
-
Carlos E. R.
-
Felix Miata
-
James Knott
-
jdd
-
Ken Schneider - openSUSE
-
Lars Müller
-
Michal Kubecek
-
Michal Kubeček
-
Per Jessen
-
Richard Brown
-
Roger Luedecke
-
Ruediger Meier
-
Rüdiger Meier
-
Sid Boyce
-
Stefan Seyfried
-
Vahis