Am 14.04.2013 00:34, schrieb Cristian Rodríguez:
El 13/04/13 19:19, Stefan Seyfried escribió:
Nobody fixes systemd bugs is my observation. Only new ones are added all the time :-)
That's not true.
My machine has been unable to shut down without sysrq-E and sometimes sysrq-I. It hangs somewhere, but because everything is totally silent it does not show any debugging output.
did you enabled debugging ?
That's not feasible as I need to enable debugging at boot and then have lots debug information wasting cycles just to debug the shutdown 2 weeks later once a new kernel is out. Or is there a way to enable debugging just before shutdown? I have not found one.
I have given up on reporting systemd bugs because they reappear faster than you can report them.
do you have examples ?
My cryptohome does not mount every second boot. This time it was actually asking me for the password on the text console and echoing the passphrase to the terminal(!), but then at least it mounted $HOME. I think I have reported cryptohome mount problems at least three times in bugzilla, but I'm just tired of it. Forwarding to syslog-ng does not work. Only "Forwarding to syslog missed XXX messages" all the time. Wait, scrap that. Since yesterday's reboot it seems to work, only ~130 missed messages during boot, now it works. (and no, journal is not an alternative, because the performance is abysmal. "journalctl", then hitting "end" thrashes my disk for about three minutes before responding. I can grep through 3 Years worth of /var/log/messages-* in the same time).
Right now I would appreciate a working SysV-Init implementation we had for 20 years much more than the ever changing and ever broken crap that systemd is.
It is not.
Maybe it works for you, but for me it is an nondeterministic heap of crap. Latest example: Curiously after timedatectl was mentioned in this hread, I issued "timedatectl" as a nonprivileged user(!) to see what it would give me. Now I no longer can start / stop ntp and ntp is broken. WTF? (Yes, I killed all involved processes I could find in the mean time). Probably the solution will be a reboot. Systemd really brings us closer to the other "great" Desktop OS's. Initially I was thinking that systemd was a good idea, right now I'm seriously considering switching to a busybox based home-built primitive init that *just works* in a deterministic way (I have about 20 different systems sitting in my A/V shelf, all running different busybox-based init systems just fine and very reliably). In theory, systemd should be more deterministic, but obviously it is only tested in very few different scenarios and mine (a pretty normal, moderately old laptop with bluetooth and wireless networking used and an encrypted $HOME) is not one of them. Probably it's too exotic. Encryption is only for terrorists and as such not supported :-) At least I'll use busybox init as an alternative implementation to get the system up when systemd fails. -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org