El 13/04/13 20:34, Stefan Seyfried escribió:
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.
didnt this --> http://freedesktop.org/wiki/Software/systemd/Debugging help ? are you sure the "freeze" is caused by systemd ? maybe be kernel bug..just saying...
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.
There were bugs, in the next iteration of systemd there are fixes included for that.
Forwarding to syslog-ng does not work. Only "Forwarding to syslog missed XXX messages" all the time.
have you considered that might be a bug in syslog-ng units and nothing to do with systemd ? (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).
Since systemd 195 there have been a lot of improvements into the journal, I suggest you test and report what happends with systemd > 201
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.
timedatectl does not cause any misbehaviour here and well, NTPD is not integrated with timedatectl/timedated in 12.3 .. it does not have native units and does not have hooks into it, this is not a bug of systemd but on the ntp package. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org