From Fedora Project Wiki
Testing Systemd new package scriptlets
Environment
Fedora 15 i686
Test package: ser2net (with fixed draft scriptlets).
New install (not upgrade)
# Check that package is not installed [spot@f15 ~]$ rpm -q ser2net package ser2net is not installed # Make sure there are no legacy SysV scripts for ser2net [spot@f15 ~]$ chkconfig --list ser2net Note: This output shows SysV services only and does not include native systemd services. SysV configuration data might be overriden by native systemd configuration. error reading information on service ser2net: No such file or directory # Confirm that systemctl doesn't know about ser2net [spot@f15 ~]$ sudo systemctl -a | grep ser2net # Install ser2net package [spot@f15 ~]$ sudo rpm -ivh /home/spot/rpmbuild/RPMS/i686/ser2net-2.7-3.fc15.i686.rpm Preparing... ########################################### [100%] 1:ser2net ########################################### [100%] # Confirm that systemctl sees ser2net and that it is not running. [spot@f15 ~]$ sudo systemctl -a |grep ser2net ser2net.service loaded inactive dead Proxy that allows tcp co [spot@f15 ~]$ ps ax |grep ser2net 20232 pts/0 S+ 0:00 grep --color=auto ser2net # Manually start ser2net.service with systemctl [spot@f15 ~]$ sudo systemctl start ser2net.service # Confirm successful startup [spot@f15 ~]$ systemctl -a |grep ser2net ser2net.service loaded active running Proxy that allows tcp co [spot@f15 ~]$ ps ax |grep ser2net 20241 ? S 0:00 /usr/sbin/ser2net 20245 pts/0 S+ 0:00 grep --color=auto ser2net # Remove ser2net package [spot@f15 ~]$ sudo rpm -e ser2net # Confirm service is no longer running [spot@f15 ~]$ ps ax |grep ser2net 20256 pts/0 S+ 0:00 grep --color=auto ser2net # Confirm that systemctl knows the service is disabled [spot@f15 ~]$ systemctl -a |grep ser2net ser2net.service error inactive dead ser2net.service # This is ugly, but systemd won't let me start it again. [spot@f15 ~]$ sudo systemctl start ser2net.service Failed to issue method call: Unit ser2net.service failed to load: No such file or directory. See system logs and 'systemctl status' for details.