on 03/12/2011 10:55 Matthew Seaman said the following: > On 03/12/2011 08:38, Chris Rees wrote: >> A little service magic would do; >> >> [ service blargh status 2>/dev/null ] && echo "DON'T FORGET TO STOP >> THIS SERVICE!!!" >> >> I'll prepare a patch, as long as there's some chance of it going in ;) > > Of course, there's always the problem that the service may be being > deleted entirely, or may radically change the way it manages start/stop > of its daemons, so you get left with a bunch of old daemons still > running and no foolproof way of identifying and stopping them. > > It's all down to ports not having an 'update' target per se, and > conceptually turning that into 'deinstall, install' -- you can't tell > that any particular 'deinstall' invocation is intended to be closely > followed by a new install or not.
You speak theoretically and you are right. But can anyone tell me (including port's maintainer) why for example smartd has to do that? It has only one daemon which is trivially identifiable and which can not do any possible harm while running (although it may let harm happen when _not_ running). -- Andriy Gapon _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
