Re: cvs commit: squid/src Makefile.am

The short story: Because it is often installed as a daemon, and if it is
classified as a bin_PROGRAM in the Makefile.am it is impossible to get it
installed in sbin without manually moving it around.

Note: Many of the things you have in sbin is indeed executable as a normal
user, but the fact that a user can run them do not make them more suitable to
be in bin..

bin is for programs a user should run as part of his daily work. squidclient
is a good candidate for bin on a Squid server..

sbin is for programs that is mainly run by the system, such as daemons or
system configuration utilities. squid is typically a deamon even if it in
certain configurations can be started by a normal user.

libexec for programs run by programs.

If you disagree, use --sbindir=...

Regards
Henrik

Robert Collins wrote:
> Why? Squid runs quite happily as a user binary, non-suid, on high port
> numbers, as well as as a chrooted app or a traditional daemon...
>
> Rob
> ----- Original Message -----
> From: <hno@squid-cache.org>
> To: <squid-cvs@squid-cache.org>
> Sent: Saturday, July 13, 2002 1:00 AM
> Subject: cvs commit: squid/src Makefile.am
>
> > hno 2002/07/12 09:00:10 MDT
> >
> > Modified files:
> > src Makefile.am
> > Log:
> > Moved squid to sbin
> >
> > Revision Changes Path
> > 1.27 +3 -1 squid/src/Makefile.am
Received on Fri Jul 12 2002 - 11:27:38 MDT