Arch Linux

Perhaps you could propose an actual service as well. You're well suited for it, since you actually use it.

I was actually working on it when I first posted the ticket, but I couldn't seem to get the tomcat service to start with the commands I was running.

Oddly the commands work fine in a regular shell or in a shell script, but when run through systemd tomcat dies with a string out of bounds error. I'm not sure what the root cause of the error is at this point.

Well, it looks like we can just reference the rc.d. That said if the person does not have sysvinit scripts installed on their machine they will run into some log messages about missing file references. Since the add_daemon, get_busy, and stat_* functions don't do anything useful in a systemd environment, the messages are really of no harm or concern. It would be better to have a separate file which runs the same commands used in the rc.d file and also includes the conf.d environment file. Aside from that, here is my working version of the tomcat service and socket.

Socket units mean that the service is socket activated, or instanced (via inetd). This isn't the case here. There's absolutely nothing gained by wrapping the /etc/rc.d script, either.

I'm totally ignorant when it comes to systemd but as I thought about giving it a try I will consider this.

Taken care of in 7.0.29-1.
@Webhostbudd: Feedback would be appreciated :)

Thanks for this update. I now get this error when trying to launch Tomcat:

$ sudo systemctl start tomcat7
Failed to issue method call: Unit tomcat7.service failed to load: No such file or directory. See system logs and 'systemctl status tomcat7.service' for details.

$ sudo systemctl status tomcat7
tomcat7.service
Loaded: error (Reason: No such file or directory)
Active: failed (Result: exit-code) since Mon, 20 Aug 2012 12:18:39 +0300; 24h ago
Main PID: 2019 (code=exited, status=143)

journalctl and /var/log/tomcat7 do not contain anything relevant. I'm new to systemd too, so I don't know how to debug this further.

> Unit tomcat7.service failed to load: No such file or directory
Could you please check /lib/systemd/system/tomcat7.service is present

I have always used the '.service' post part for my tests:
# systemctl start tomcat7.service

Could you please try this (I know the error message states 'tomcat7.service' but let's try).

$ ls -l /lib/systemd/system/tomcat7.service
-rw-r--r-- 1 root root 1049 Aug 19 17:08 /lib/systemd/system/tomcat7.service

$ sudo systemctl start tomcat7.service
Failed to issue method call: Unit tomcat7.service failed to load: No such file or directory. See system logs and 'systemctl status tomcat7.service' for details.

$ sudo systemctl status tomcat7.service
tomcat7.service
Loaded: error (Reason: No such file or directory)
Active: failed (Result: exit-code) since Mon, 20 Aug 2012 12:18:39 +0300; 24h ago
Main PID: 2019 (code=exited, status=143)

Run one of the following:
# systemctl daemon-reload
# kill -1 1

Until then, systemd will not read newly installed (or updated) unit files.

Thanks, that seems to do the trick. Sorry for the noise on this report.

The kill call was not necessary.

Thanks for this Dave.