On Wed, Jun 20, 2012 at 05:59:09PM +0200, Reindl Harald wrote:
> i saw a dist-upgrade on the fist-testmachine restart httpd
> which failed for some reason and AFTER some time you could
> start httpd again
Leaving version X of /usr/sbin/httpd running after version Y of
/usr/sbin/httpd is installed
On 06/21/2012 11:01 PM, Reindl Harald wrote:
Am 21.06.2012 22:52, schrieb Michal Hlavinka:
On 06/20/2012 02:37 PM, Reindl Harald wrote:
Am 20.06.2012 14:32, schrieb Björn Persson:
Michal Hlavinka wrote:
Correct approach would be to save state before installation of new
version starts and
On Thu, Jun 21, 2012 at 11:01:16PM +0200, Reindl Harald wrote:
> >>
> >> one reason more why the cuurent behavior re-starting services
> >> on updates is simply wrong:
> >
> > You complained that service is restarted during update. Well, in this case,
> > restart is not sufficient. We even have
>
Am 21.06.2012 22:52, schrieb Michal Hlavinka:
> On 06/20/2012 02:37 PM, Reindl Harald wrote:
>>
>>
>> Am 20.06.2012 14:32, schrieb Björn Persson:
>>> Michal Hlavinka wrote:
Correct approach would be to save state before installation of new
version starts and start dovecot (if flag is se
On 06/20/2012 02:37 PM, Reindl Harald wrote:
Am 20.06.2012 14:32, schrieb Björn Persson:
Michal Hlavinka wrote:
Correct approach would be to save state before installation of new
version starts and start dovecot (if flag is set) after old version is
removed - that would mean %postun script. T
Am 20.06.2012 18:26, schrieb Panu Matilainen:
>> i was there, i saw was happened on dist-upgrades, i fixed them
>>
>> i saw a dist-upgrade on the fist-testmachine restart httpd
>> which failed for some reason and AFTER some time you could
>> start httpd again
>>
>> * i rebuilt the httpd package
>>
On 06/20/2012 06:59 PM, Reindl Harald wrote:
Am 20.06.2012 17:42, schrieb Panu Matilainen:
On 06/20/2012 03:37 PM, Reindl Harald wrote:
Am 20.06.2012 14:32, schrieb Björn Persson:
Michal Hlavinka wrote:
Correct approach would be to save state before installation of new
version starts and
Am 20.06.2012 17:42, schrieb Panu Matilainen:
> On 06/20/2012 03:37 PM, Reindl Harald wrote:
>>
>>
>> Am 20.06.2012 14:32, schrieb Björn Persson:
>>> Michal Hlavinka wrote:
Correct approach would be to save state before installation of new
version starts and start dovecot (if flag is se
On 06/20/2012 06:42 PM, Panu Matilainen wrote:
On 06/20/2012 03:37 PM, Reindl Harald wrote:
Am 20.06.2012 14:32, schrieb Björn Persson:
Michal Hlavinka wrote:
Correct approach would be to save state before installation of new
version starts and start dovecot (if flag is set) after old versio
On 06/20/2012 03:37 PM, Reindl Harald wrote:
Am 20.06.2012 14:32, schrieb Björn Persson:
Michal Hlavinka wrote:
Correct approach would be to save state before installation of new
version starts and start dovecot (if flag is set) after old version is
removed - that would mean %postun script. T
Am 20.06.2012 14:32, schrieb Björn Persson:
> Michal Hlavinka wrote:
>> Correct approach would be to save state before installation of new
>> version starts and start dovecot (if flag is set) after old version is
>> removed - that would mean %postun script. This does not seem to work on
>> rei
Michal Hlavinka wrote:
> Correct approach would be to save state before installation of new
> version starts and start dovecot (if flag is set) after old version is
> removed - that would mean %postun script. This does not seem to work on
> reinstall (the same version is installed) - %postun scr
Hi,
I'm trying to find out what is the best place to restart service after
update. Dovecot have runs several binaries, has some plugins,... in
short, it does not like when it's running during update. I was asked by
upstream to modify rpm package to stop it before update and start it
afterward
13 matches
Mail list logo
