On 02/10/2012 01:05 PM, Michal Schmidt wrote:
Ralf Corsepius wrote:
Let me put it this way: I am having difficulties in recalling any
Fedora release which worked for me out of the box ...
In earlier releases there for example were pulseaudio and SELinux, in
current releases it's primarily systemd
What kind of problems in the out of the box setup are you seeing with
systemd?
I have been facing 3 kind of major issues related to systemd:
a) yum upgrading from f14->f16 did not cleanup /etc/rc?.d, leaving
dangling symlinks behind, seemingly causing systemd to get confused.
In some cases the machines fortunately came up to a point, I could
manually clean up the symlinks.
b) Machines not coming up properly after upgrades and sending me into
- In one case, seemingly xserver failed, ... I found myself on console
filed with systemd error messages, with no option to do anything.
- In another case, I ended up in some sort of systemd emergency shell,
confronted with some cryptic error messages, which left me clueless (I
know how to use an emergency shell, it's just that I had no idea what to
do about these error messages)
c) Systemd doesn't seem to preserve existing activated services upon
update (I recall having to manually activate cron and rsyslog).
There are other minor issues, which sporadically show up, such as some
network related services (vsftpd, yp, named, ntpd, autofs, ...) not
coming up after reboots, but I am not sure if it's really systemd who is
to blame or something else.
Could you give me any Bugzilla links?
Unfortunatly, except of the vsftpd issue, no - My fault, sorry, but when
upgrading, I am focusing on getting the machine up again ;)
Ralf
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
