[opensuse-factory] systemd issues
This is a factory build 45 system, minimal server install. I've noticed some differences when I boot with systemd: acpid is not started. rsyslogd is not started with sysvinit I would have a set of virtual consoles: /sbin/mingetty --noclear tty1 /sbin/mingetty tty2 /sbin/mingetty tty3 /sbin/mingetty tty4 /sbin/mingetty tty5 /sbin/mingetty tty6 with systemd I have: /sbin/agetty tty1 38400 /sbin/agetty tty2 38400 /sbin/agetty tty3 38400 /sbin/agetty tty4 38400 /sbin/agetty tty5 38400 /sbin/agetty tty6 38400 -- Per Jessen, Zürich (21.0°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sun, 2011-06-12 at 15:06 +0200, Per Jessen wrote:
This is a factory build 45 system, minimal server install.
I've noticed some differences when I boot with systemd:
acpid is not started. rsyslogd is not started
The spec files do not enable them. The current sysv enabled-state needs to be mirrored to systemd's state on upgrade. It's being worked on. For now you need to do it manually: systemctl enable rsyslog.service systemctl enable acpid.service
with sysvinit I would have a set of virtual consoles:
/sbin/mingetty --noclear tty1 /sbin/mingetty tty2 /sbin/mingetty tty3 /sbin/mingetty tty4 /sbin/mingetty tty5 /sbin/mingetty tty6
with systemd I have:
/sbin/agetty tty1 38400 /sbin/agetty tty2 38400 /sbin/agetty tty3 38400 /sbin/agetty tty4 38400 /sbin/agetty tty5 38400 /sbin/agetty tty6 38400
That's expected. mingetty is no longer used with systemd, and all distros using systemd standardized on util-linux's agetty for everything. Kay -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Kay Sievers wrote:
On Sun, 2011-06-12 at 15:06 +0200, Per Jessen wrote:
This is a factory build 45 system, minimal server install.
I've noticed some differences when I boot with systemd:
acpid is not started. rsyslogd is not started
The spec files do not enable them. The current sysv enabled-state needs to be mirrored to systemd's state on upgrade. It's being worked on.
For now you need to do it manually: systemctl enable rsyslog.service systemctl enable acpid.service
Okay, thanks. rsyslog.service doesn't seem to exist: # systemctl enable rsyslog.service Couldn't find rsyslog.service. I've probably misunderstood this, but I thought systemd would be compatible with existing sysv init scripts?
That's expected. mingetty is no longer used with systemd, and all distros using systemd standardized on util-linux's agetty for everything.
Could this be causing or affecting the garbled console output I'm seeing? Not the best of pictures, but still: http://files.jessen.ch/guest53-console.jpg -- Per Jessen, Zürich (21.1°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Per Jessen wrote:
Kay Sievers wrote:
On Sun, 2011-06-12 at 15:06 +0200, Per Jessen wrote:
This is a factory build 45 system, minimal server install.
I've noticed some differences when I boot with systemd:
acpid is not started. rsyslogd is not started
The spec files do not enable them. The current sysv enabled-state needs to be mirrored to systemd's state on upgrade. It's being worked on.
For now you need to do it manually: systemctl enable rsyslog.service systemctl enable acpid.service
Okay, thanks.
Oops, cron doesn't start either.
I've probably misunderstood this, but I thought systemd would be compatible with existing sysv init scripts?
Hmm, no, seems to work fine, I've just installed the HP Proliant support pack 8.70, no problems with systemd.
Could this be causing or affecting the garbled console output I'm seeing? Not the best of pictures, but still: http://files.jessen.ch/guest53-console.jpg
Try the following too: login on console1, ps axfl, logout - the new login prompt now starts at the top of the screen, but the screen hasn't been cleared. With mingetty, the console worked more like a real console, i.e. it scrolled bottom-to-top. -- Per Jessen, Zürich (22.5°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
sø., 12.06.2011 kl. 16.44 +0200, skrev Per Jessen:
For now you need to do it manually: systemctl enable rsyslog.service systemctl enable acpid.service
Okay, thanks.
Oops, cron doesn't start either.
Works here. Could it be that systemd has issues with booting from lilo? embla:/ # systemctl status syslog.service syslog.service - LSB: Start the system logging daemons Loaded: loaded (/etc/init.d/syslog) Active: active (running) since Sun, 12 Jun 2011 09:11:44 +0200; 7h ago Process: 948 ExecStart=/etc/init.d/syslog start (code=exited, status=0/SUCCESS) Main PID: 1101 (rsyslogd) CGroup: name=systemd:/system/syslog.service └ 1101 /sbin/rsyslogd -c 5 -f /etc/rsyslog.conf embla:/ # systemctl status cron.service cron.service - LSB: Cron job service Loaded: loaded (/etc/init.d/cron) Active: active (running) since Sun, 12 Jun 2011 09:11:44 +0200; 7h ago Process: 1443 ExecStart=/etc/init.d/cron start (code=exited, status=0/SUCCESS) Main PID: 1464 (cron) CGroup: name=systemd:/system/cron.service └ 1464 /usr/sbin/cron embla:/ # systemctl status acpid.service acpid.service - LSB: Listen and dispatch ACPI events from the kernel Loaded: loaded (/etc/init.d/acpid) Active: active (running) since Sun, 12 Jun 2011 09:11:39 +0200; 7h ago Process: 771 ExecStart=/etc/init.d/acpid start (code=exited, status=0/SUCCESS) Main PID: 810 (acpid) CGroup: name=systemd:/system/acpid.service └ 810 /sbin/acpid embla:/ # -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Bjørn Lie wrote:
sø., 12.06.2011 kl. 16.44 +0200, skrev Per Jessen:
For now you need to do it manually: systemctl enable rsyslog.service systemctl enable acpid.service
Okay, thanks.
Oops, cron doesn't start either.
Works here. Could it be that systemd has issues with booting from lilo?
apart from syslog, acpid and cron also start, but I had to activate/insert them manually. # systemctl status syslog.service syslog.service - LSB: Start the system logging daemons Loaded: loaded (/etc/init.d/syslog) Active: inactive (dead) CGroup: name=systemd:/system/syslog.service When I start syslog manually, it works. -- Per Jessen, Zürich (15.9°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Sun, 12 Jun 2011 16:44:47 +0200 schrieb Per Jessen <per@opensuse.org>:
login on console1, ps axfl, logout - the new login prompt now starts at the top of the screen, but the screen hasn't been cleared. With mingetty, the console worked more like a real console, i.e. it scrolled bottom-to-top.
This is not an agetty problem, this worked fine until a few days ago, now it fails. It's a regression, those happen. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Stefan Seyfried wrote:
Am Sun, 12 Jun 2011 16:44:47 +0200 schrieb Per Jessen <per@opensuse.org>:
login on console1, ps axfl, logout - the new login prompt now starts at the top of the screen, but the screen hasn't been cleared. With mingetty, the console worked more like a real console, i.e. it scrolled bottom-to-top.
This is not an agetty problem, this worked fine until a few days ago, now it fails. It's a regression, those happen.
Sure, okay. -- Per Jessen, Zürich (15.9°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (4)
-
Bjørn Lie -
Kay Sievers -
Per Jessen -
Stefan Seyfried