Jay DeKing [EMAIL PROTECTED] writes:
Lots of people edit them. And they only don't get replaced when
they've been changed. Otherwise it's not a problem. So if you
edit one and upgrade it hopefully you're smart enough to look for
the .rpmnew file.
I edit a LOT of them, and would not
On Tuesday 28 May 2002 02:23 am, Ben Reser wrote:
On Tue, May 28, 2002 at 10:06:09AM +0400, Borsenkow Andrej wrote:
Is there any policy related to init scripts? I see absolutely no reasons
to define them as noreplace except for very special cases (like rc.local
probably).
Lots of people
On Tue, May 28, 2002 at 10:06:09AM +0400, Borsenkow Andrej wrote:
Is there any policy related to init scripts? I see absolutely no reasons to
define them as noreplace except for very special cases (like rc.local
probably).
Lots of people edit them. And they only don't get replaced when
Borsenkow Andrej [EMAIL PROTECTED] writes:
Most init scripts I have seen are defined as noreplace. It has unfortunate
effect - if init script is changed, it is not replaced. It means that in
postinstall section rpm actually runs restart with _old_ script. Which is
obviously wrong (exactly in
Most init scripts I have seen are defined as noreplace. It has unfortunate
effect - if init script is changed, it is not replaced. It means that in
postinstall section rpm actually runs restart with _old_ script. Which is
obviously wrong (exactly in case when script has changed).
Is there any
