Am 16.09.2011 11:51, schrieb Lev Serebryakov:
Hello, Freebsd-ports.
You wrote 16 сентября 2011 г., 0:28:07:
Really? I thought it was supposed to be standard behaviour- the @stopdaemon
line in pkg-plist facilitates that.
While I totally understand why we do this, I have to say it's VERY
We do not currently have a standard procedure for that, nor do we record
the necessary state -- perhaps we should just discuss, vote, and add a
paragraph to the porter's handbook.
We also need to bring the authors (or volunteers) for the de-facto
standard upgrade tools into the loop.
My
W dniu 2011-09-16 18:17, Eric pisze:
Just for ref regarding (c) on the portupgrade wiki page[1] it mentions using
AFTERINSTALL in pkgtools.conf for doing automatic stop/start/restart.
I'm using it for a long time on my personal box and it's not that great.
After some updates there is need to
2011/9/16 Łukasz Wąsikowski luk...@wasikowski.net:
W dniu 2011-09-16 18:17, Eric pisze:
Just for ref regarding (c) on the portupgrade wiki page[1] it mentions using
AFTERINSTALL in pkgtools.conf for doing automatic stop/start/restart.
I'm using it for a long time on my personal box and it's
Hello, Łukasz.
You wrote 16 сентября 2011 г., 22:17:58:
were not recompiled). Updating ports should never turn off or restart
service - thats my $0.02.
I agree with that. It is not difficult to REstart service by hands.
But stopping service is another story. Many ports/packages stop
W dniu 2011-09-16 20:25, Chris Rees pisze:
However, having services not restarted after an upgrade can leave you
with a) a vulnerable older service and b) a nasty shock when you
decide to reboot six months later and it breaks :)
I know that I should restart service after update and I will do
Lev Serebryakov wrote:
Hello, Łukasz.
You wrote 16 сентября 2011 г., 22:17:58:
were not recompiled). Updating ports should never turn off or restart
service - thats my $0.02.
I agree with that. It is not difficult to REstart service by hands.
But stopping service is another story. Many
