03b7b20ce7aa394d80c159de55c7ec2c69f3849c
SysV init scripts are ran on boot from symlinks in `/etc/rc.d/rc.X`, where X is the runlevel. These symlinks are usually named something like `S99foobar`, which is a link to the real script `foobar`. This leads to differences in the pid_file filename and can lead to multiple processes running. By using readlink to get the actual destination filename, the pid_file name should always be consistent. Resolves: #78
…
service 
service will install / un-install, start / stop, and run a program as a service (daemon). Currently supports Windows XP+, Linux/(systemd | Upstart | SysV), and OSX/Launchd.
Windows controls services by setting up callbacks that is non-trivial. This is very different then other systems. This package provides the same API despite the substantial differences. It also can be used to detect how a program is called, from an interactive terminal or from a service manager.
BUGS
- Dependencies field is not implemented for Linux systems and Launchd.
- OS X when running as a UserService Interactive will not be accurate.
Description
Languages
Go
98.4%
Makefile
1%
Shell
0.3%
Dockerfile
0.3%