Re: Bug#548230: dropbear: configuration in /etc/<package> does not follow FHS
On Tue, Sep 29, 2009 at 04:39:43PM -0600, Bdale Garbee wrote:
> Gerrit, in reviewing the dropbear package source, I couldn't help but
> wonder why /etc/dropbear/log/run specifies ./main as the log file? That
> motivates use of a symlink to point /etc/dropbear/log/main
> to /var/log/dropbear. Wouldn't it be simpler and cleaner to just
> specify /var/log/dropbear as the last argument to svlogd in that script,
> and thus avoid another level of useless indirection?
Yes, possibly. But it's not completely useless, with the symlink in
log/, all service related data is consolidated in one directory. With
runit and daemontools managed services, you can cd into the service
directory, and have all data you need conveniently available without
looking up where which data actually is saved in the filesystem. You
have the service configuration in ./run (and possibly ./config or
similar), the log service configuration in ./log/run, the logs in
./log/main/, and optionally log specific configuration in
./log/main/config. If that's consistent throughout all supervised
services, I personally find that useful.
> Gerrit, in reviewing other instances of runit support, I do find some
> inconsistency in where things are delivered. The fact that dropbear is
> delivering these files to /etc/dropbear but git-daemon-run
> uses /etc/sv/git-daemon seems inconsistent to me, for example. While
> that's completely orthogonal to this request of the Tech Ctte, settling
> on one approach might make it easier for others like me to read and
> comprehend what's being delivered.
True, you're right. I did the dropbear package in 2004, and introduced
/etc/sv/ not before 2006. I didn't move the directory because of two
reasons. (1) moving conffiles was not trivial (in the meantime I have
code in some packages that do that), (2) the dropbear package ships
both, a sysv init script and a runit service directory. sysv users
look for the configuration in /etc/dropbear/, and runit users in
/etc/sv/dropbear/. /etc/dropbear/ holds the host keys which are used
by both service startup methods. I'm not sure whether a symlink
/etc/sv/dropbear -> /etc/dropbear would help, or rather complicate
things again.
Regards, Gerrit.
Reply to: