|
From: Tom E. <te...@sh...> - 2015-02-08 01:58:56
|
On 2/7/2015 5:52 PM, h1...@ma... wrote: > Nah, the problem's not how to start / stop shorewall. > > The question is WHY a package upgrade causes it to choke killing off network & requiring a restart. > > Just for yuck I tried it on a remote box over SSH access (I have remote access via another channel; it's a hosted VM, and you can get to a login via a console session -- no network required). > > And yep. In the middle of the shorewall package upgrade, the connection just drops. When I checked, the network is completely "inaccessible". No pings anywhere. Restart networok & shorewall -- by any number of ways -- and I'm back up. > > So 'something' during that package upgrade is killing more than it should. Dunno what yet. > > I'd think that a package upgrade should generally do that 'gracefully'. > You need to be reporting this problem to SuSE -- there is nothing we can do on this list to change the behavior of a distro's package upgrade. If the SuSE maintainer determines that there is a problem with the base Shorewall code, he and I can work together to resolve it. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ |