Systemd service for packages without support

[Marcos Alano]

This bug is a little (just a little!?) crazy: First I done some shell-fu:

apt-file search /lib/systemd/system/|grep service|cut -d: -f1|uniq > systemd_service.txt
apt-file search /etc/init.d/|cut -d: -f1|uniq > sysvinit_service.txt
diff systemd_service.txt sysvinit_service.txt|grep '^\+' >just_sysvinit.txt

The first command created a list with the packages with systemd services. I considered as systemd service any package with a .service file under /lib/systemd/system/.

The second command created a list with the packages with sysvinit services. I considered a sysvinit service any package with a file under /etc/init.d/.

The third command compares the two files and only select the packages with sysvinit service, but without a correspondent systemd service. This packages should have support for systemd too because systemd is now native on new Ubuntu releases. I don't think need hurry to change all packages because sysvinit support on systemd is solid, but I think we need to think about this.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1681993/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]