Red Hat Bugzilla – Bug 825871
'service dirsrv start' no longer works
Last modified: 2013-03-04 17:38:32 EST
The 'service' binary is intended to work as a backwards-compatibility wrapper around systemd. However, 'service start dirsrv' no longer works, because you must start dirsrv using 'systemctl start dirsrv.target', not 'systemctl start dirsrv.service'. The latter fails with "No such file or directory."
If we were to support service, things like service start dirsrv inst-name would not work, nor is there a way to make it work, meaning the service command would work differently on systemd platforms and non-systemd platforms. Is this acceptable?
I don't mind if you don't support service; but it shouldn't fail silently. ;-)
In particular: [root@whole-enchilada ~]# service dirsrv stop Redirecting to /bin/systemctl stop dirsrv.service [root@whole-enchilada ~]# echo $? 0 [root@whole-enchilada ~]# systemctl status dirsrv@scripts.service dirsrv@scripts.service - 389 Directory Server scripts. Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service; enabled) Active: active (running) since Thu, 31 May 2012 23:00:33 -0400; 1 day and 12h ago Process: 2947 ExecStopPost=/bin/rm -f /var/run/dirsrv/slapd-%i.pid (code=exited, status=0/SUCCESS) Process: 3292 ExecStart=/usr/sbin/ns-slapd -D /etc/dirsrv/slapd-%i -i /var/run/dirsrv/slapd-%i.pid -w /var/run/dirsrv/slapd-%i.startpid (code=exited, status=0/SUCCESS) Main PID: 3293 (ns-slapd) CGroup: name=systemd:/system/dirsrv@.service/scripts └ 3293 /usr/sbin/ns-slapd -D /etc/dirsrv/slapd-scripts -i /var/run/dirsrv/slapd-scripts.pid -w /var/run/dirsrv/slapd-scrip...
Upstream ticket: https://fedorahosted.org/389/ticket/423
The silent failing issue was fixed in upstream ticket 457, which went out in 389-ds-base-1.2.11.15-1: https://fedorahosted.org/389/ticket/457 That said, the service command is not supported. Closing this ticket.