ssm-services/conf.d
2015-09-09 12:20:58 +02:00
..
devfs-links.sh some default useful links 2015-02-08 03:17:49 +03:00
dnscrypt-backup.sh Update dnscrypt-backup.sh 2014-07-21 18:14:13 +02:00
dnscrypt.sh Create dnscrypt.sh 2014-07-21 18:12:57 +02:00
dropbear.sh So, as an example of the way conf.d is supposed to be used, I've provided 2014-07-06 11:13:39 +04:00
fcgiwrap.sh I keep forgetting how my own services work 2014-07-31 01:14:25 +04:00
kmscon.sh tty1 should exist even if not enabled 2014-07-21 20:26:43 +04:00
ldm.sh Create ldm.sh 2015-09-09 12:20:58 +02:00
ngetty.sh ngetty 2015-02-14 16:25:12 +03:00
README READMEs in the config dirs 2014-07-06 18:32:34 +04:00

This is the directory additional service configuration is sourced from.
Basically you can override what's written in a service file from here
without directly modifying the service itself, making it easier to
update those as any local configuration should go here instead.

I've provided a sample conf.d entry for dropbear to demostrate.