> > - You might want to provide a symbolic link so that users can access > > lighttpd from /usr/lighttpd/bin like the same way we have done for PHP > > and MySQL. > > What's the logic behind that? Is it mainly to make it easier to get to?
Yes but let's also consider the distinction between bins meant for human consumption vs. those which are not. We don't, for example, link /usr/apache2/2.2/bin/httpd from elsewhere because the normal use case is to start it via smf, so the binary being in an inconvenient location is of no consequence. smf knows how to find it and that's all that matters. lighttpd is also a web server so naturally falls in the same category. Just start via smf and it'll "just work". I remember the earlier comments here about some people starting lighttpd manually from the CLI. The thread didn't go far so I didn't see a conclusion on whether that's a primary use case or not. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
