Useful init scripts to Linux Systems.

Óscar García Amor 91de058980 Systemd gitlab scripts updated 4 years ago
runit d5040d9c8d Add runit scripts 6 years ago
systemd 91de058980 Systemd gitlab scripts updated 4 years ago
sysv f79c652b8b Added OpenConnect init script to use with System V 5 years ago
upstart ffa6fb149d Better Tomcat Upstart script 6 years ago
LICENSE a858435643 Add license 5 years ago
README.md 74b6da1ac1 Fixed small typo in README 5 years ago

README.md

Init Scripts

Useful init scripts to Linux Systems.

To install this init scripts you must copy it to proper folder

runit

The scripts in runit folder could be copied to /etc/runit in most systems, where runsvdir parse them (check runit documentation for your OS for more information, because of the path can change in some distributions). Our recomendation is to put these files in other path /etc/sv and (soft) linking them to /etc/runit, to avoid unwanted running actions.

systemd

The scripts in systemd folder must be copied to /usr/lib/systemd/system. When a new script is added to this folder (or a script has been modified) you must execute systemctl daemon-reload to reload it into systemd. To enable the scripts you must execute systemctl enable service (being service the name of the script without .service extension).

System V

The scripts in sysv folder must be copied to /etc/init.d and enabled with update-rc.dcommand in Debian or with chkconfig in Red Hat.

Upstart

The scripts in upstart folder must be copied to /etc/init and don't need to enable them because this occurs automagically. You can make a symbolic link in /etc/init.d folder with the same name to /lib/init/upstart-job for use the old fashion /etc/init.d/script start|stop|restart....