Re: service directory name

[Mark Delany <markd-qmail@xxxxxxxxxxxx>]

On Sat, Mar 02, 2002 at 09:14:28AM -0500, Russell Nelson allegedly wrote:
> Tetsu Ushijima writes:
>  > Marcus Bointon writes:
>  > > You'll also find that much of the documentation is inconsistent in the
>  > > naming of things. I've made sure I always use the style 'qmail-pop3d' and
>  > > not 'pop3d' wherever things like that are mentioned, including in the
>  > > supervise log scripts. This has made my installation much tidier and easier
>  > > to read.
>  > 
>  > In the qmail-conf documentation, I followed publicfile/configure's
>  > convention. Given that we use /service/ftpd for an FTP service and
>  > /service/httpd for an HTTP service, why not use /service/smtpd for
>  > an SMTP service and /service/pop3d for a POP3 service?
> 
> Indeed.  I do the same thing as my customer's sites.  I have no
> expectation that there will ever be a /service/postfix-pop3d, so why
> have a "qmail-" on these services?

Almost indeed for me. For systems that share internal and external
responsibilities (a lot of the small fry) I use something like this:

/service/httpd-external  /service/smtpd-external
/service/httpd-internal  /service/smtpd-internal
/service/popd-internal

For the obvious reasons that they are listening on different
interfaces and have different resource settings.

Additionally, I kinda like the idea of being able to easily control
all external services with: svc -{d|t} /service/*-external. This can
be useful in an emergency as well as for sites that are dynamically
re-IPed.


Regards.