Bug 660493

Summary: systemd: acpid and crond not starting
Product: [openSUSE] openSUSE 11.4 Reporter: Stefan Seyfried <seife>
Component: BasesystemAssignee: Kay Sievers <kasievers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: forgotten_Si7ddX0wxG, mseben
Version: Factory   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Third Party Developer/Partner Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Stefan Seyfried 2010-12-20 09:43:17 UTC
factory-101122:~ # systemctl status acpid.service
acpid.service - ACPI Event Daemon
          Loaded: loaded (/lib/systemd/system/acpid.service)
          Active: inactive (dead)
          CGroup: name=systemd:/system/acpid.service
factory-101122:~ # systemctl status cron.service
cron.service - Command Scheduler
          Loaded: loaded (/lib/systemd/system/cron.service)
          Active: inactive (dead)
          CGroup: name=systemd:/system/cron.service

factory-101122:~ # chkconfig acpid
acpid  on
factory-101122:~ # chkconfig cron
cron  on


both start fine when using SYSV init.

factory-101122:~ # cat /lib/systemd/system/acpid.service
[Unit]
Description=ACPI Event Daemon
After=syslog.target

# This could probably benefit from socket activation, but honestly I think it
# is time for acpid to go away, and hence I am not planning to spend the time
# to add socket activation here. We use Type=forking to ensure that the
# communication sockets are in place before boot proceeds with any service
# needing this service. Would acpid support socket activation we could use
# Type=simple here.

[Service]
Type=forking
ExecStart=/sbin/acpid 

[Install]
WantedBy=multi-user.target
factory-101122:~ # cat /lib/systemd/system/cron.service
[Unit]
Description=Command Scheduler
After=syslog.target mail-transfer-agent.target

[Service]
ExecStart=/usr/sbin/cron -n

[Install]
WantedBy=multi-user.target

factory-101122:~ # systemctl status syslog.target
syslog.target - Syslog
          Loaded: loaded (/lib/systemd/system/syslog.target)
          Active: inactive (dead)
factory-101122:~ # systemctl status syslog.service
syslog.service - LSB: Start the system logging daemons
      Loaded: loaded (/etc/init.d/syslog)
      Active: active (running) since Mon, 20 Dec 2010 10:36:11 +0100; 5min ago
     Process: 2016 (/etc/init.d/syslog start, code=exited, status=0/SUCCESS)
      CGroup: name=systemd:/system/syslog.service
              └ 2164 /sbin/rsyslogd -c 5 -f /etc/rsyslog.conf

factory-101122:~ # rpm -q --changelog systemd|head
* Do Dez 09 2010 kay.sievers@novell.com
- add LSB 'smtp' alias for mail-transport-agent.target

To me it looks like the syslog.target is somehow borken.
Comment 1 Kay Sievers 2010-12-20 11:17:43 UTC
You need to call:
  systemctl enable acpid.service

acpid.rpm should enable its systemd service in any case on new package *installations*.

But it is currently undecided how to do it on package *upgrades* from the spec file. See:
  https://bugzilla.novell.com/show_bug.cgi?id=659357#c3
Comment 2 Stefan Seyfried 2010-12-20 13:10:05 UTC
Ok, so it is not a bug, strictly speaking ;)

I added the info on how to enable services to http://en.opensuse.org/SDB:Systemd
Comment 3 Wei Wang 2010-12-21 05:54:15 UTC
(In reply to comment #2)
> Ok, so it is not a bug, strictly speaking ;)
> 
> I added the info on how to enable services to
> http://en.opensuse.org/SDB:Systemd

Stefan,is that means it can be closed ?
Comment 4 Kay Sievers 2010-12-21 07:54:06 UTC
I'll close it when we have a solution. Thanks!
Comment 5 Forgotten User Si7ddX0wxG 2011-02-15 00:55:05 UTC
Im using 11.4 x86-64 RC1  and crontab is not started on boot
So I do the following to get crontab going

# rccron stop
Shutting down CRON daemon 

# rccron start
Starting CRON daemon
Comment 6 Kay Sievers 2011-03-10 16:25:16 UTC
Tracked in bnc#659357.

*** This bug has been marked as a duplicate of bug 659357 ***