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'. hanlon ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
