Matt Johnston <[email protected]> writes:
> Debian runit configuration
>
> They are not log files (well, one is a symlink to /var/log/dropbear)
Please remove that one. It should only be under /var/log
/etc/dropbear $ ls -lR
drwxr-xr-x 2 root root 4096 Jul 21 15:31 log
./log:
total 4
lrwxrwxrwx 1 root root 17 Jul 21 15:18 main -> /var/log/dropbear
> or runtime status files, but rather config files for Dropbear.
/etc/dropbear $ ls -l
-rwxr-xr-x 1 root root 100 Aug 10 2007 run
$ cat run
#!/bin/sh
exec 2>&1
exec dropbear -d ./dropbear_dss_host_key -r ./dropbear_rsa_host_key -F -E
-p 22
FHS:
http://www.pathname.com/fhs/pub/fhs-2.3.html#ETCHOSTSPECIFICSYSTEMCONFIGURATION
"The /etc hierarchy contains configuration files. A "configuration
file" is a local file used to control the operation of a program; it
must be static and cannot be an executable binary."
===============================
Suggestion:
- Arrange the 'run' executable to FHS location ( /var/lib /usr/share )
- Make the 'run' executable read configuration from
/etc/dropbear/run.conf
> I see no problem with readonly program-specific configuration files
> being under /etc/dropbear, according to the FHS?
Configuration files, yes; Read-only no. Executables no. If there is a
file, it's "configurable" under /etc according to FHS.
Jari
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
