Nicolas Williams wrote: > On Wed, Aug 06, 2008 at 09:39:33PM -0700, Sriram Natarajan wrote: > >> I was wondering, if I can hear every one's thoughts as to should we >> deliver a symbolic link of apache, php and mysql binaries (at least some >> of the most commonly) used under /usr/bin ? For example, some of the >> commonly used binaries like ab, apxs, httpd, httpd.worker, php, php-cgi, >> mysql, mysqladmin should have a symbolic link under /usr/bin ? One >> argument for having this under /usr/bin is they are easy to access and >> customer clearly knows about this ? Currently, none of this are >> delivered under /usr/bin and users are expected to set >> /usr/<component>/<version> in their PATH before using these. Do we still >> follow the same pattern ? >> > > Current policy is not to put daemons in /usr/bin, nor in /usr/sbin, but > in /usr/lib. > > Do users really run 'httpd' directly? And php-cgi?! > > I meant to put these just as examples more than any thing else. > Users should not have to add /usr/<component>/... to PATH for common > executables. That was my thinking too. For example, user does not have to do /usr/mysql/5.1/bin in the PATH so that they can run mysqladmin from the command line. The same can apply for Postgres or PHP or any other component. But, I am missing a common or conventional user policy here. Hence, initiated this thread. > But daemons should generally not be run by users directly. > OTOH, there needs to be an easy way to find the location of such > daemons (the manpages usually tell you). > > Again, I agree - that is why we have SMF. Daemons should be managed with SMF.
- sriram > Nico >
