Lance Albertson wrote:
Actually, that is the intended outcome since a virtual/httpd does not
exist yet. If neither of the use flags are set, its next choice is
lighthttpd. One of the limitations/hacks I had to do in the ebuild
because of the lack of the virtual. If you feel it should be different,
please file a bug in bugzilla and I'll take a look at it :-).


Hard to say. I don't consider that behavior broken, just different than what I've grown to depend on. Also IIRC there was an explicit lack of apache1 USE variables when apache2 was introduced which is why I ran into the problem now. To get things to work the way they used to would be to require apache2 and lighthttpd flags and assume apache1 in the absence of either, but that seems retarded on some level.

In any case I added apache1 to my USE and am none the worse for the wear.

However any server profile won't be written in stone either and will need to be changed as Gentoo changes. Personally I don't see much point in creating a server profile that's too general to useful. I'd rather spend time creating some documentation about setting up servers in general. Something like.

arping, curl, fping, nmap, netcat, tcpdump, traceroute, tcptraceroute, telnet-bsd, nessus, nikto These same tools might not be such a good idea on a public server. Or maybe it's not worth the hassle to deny an attacker an extra minute or two in uploading his own tools when you likely waster 3-4 hours a year of admin time by not having them. Or when an outage event occurs it is worth the 2-3 minutes you'd save by having the right tools availible.

I think we can all argue the nuts and bolts forever, but some framework for building your own might be more interesting. In full disclosure I've rolled out 20 new servers in the last couple of months so I've got my server profile pretty much refined... for me personally. Looking through this thread I'd say that anyone using mine is only going to be happy 50% of the time... in which case they should probably build their own. :)

kashani
--
[email protected] mailing list

Reply via email to