> reasonably convinced that the correct approach is to treat it like > Apache httpd. That leaves us with /usr/lighttpd/14/sbin/lighttpd and > /usr/lighttpd/bin/spawn-fcgi as the path to the executables. Are links > necessary? I personally would prefer to type /usr/lighttpd/sbin/lighttpd > than /usr/lighttpd/14/sbin/lighttpd (and I run lighttpd several times a > day, 50% with SMF and 50% on the command line). At the same time though > I don't want to create any confusion, confusion that might arise if both > 1.4. and 1.5 are installed and the user has no idea what they are > running when they type /usr/lighttpd/sbin/lighttpd. Seems to be a case > of "easier to type" vs "more potential for confusion". I'd go with not > creating the link, users have several options for making it easier to > type. i.e.: Learn about SMF, alias it, add it to their path, etc.
Yes, I would go strictly with using SMF in this case - if a user really wants to type it on the command line, your suggestion of an alias is a good one. dsc
