-----BEGIN PGP SIGNED MESSAGE-----
On Sat, 2 Aug 2003, Nejc Skoberne wrote: > I have a problem - sometimes FreeSWAN (Pluto?) dies just like that. How do you notice that FreeS/WAN has "died"? > If I do "ps", I see this: > > 229 ? S 0:00 /bin/sh /usr/local/lib/ipsec/_plutorun --debug none > --uniqueids yes --nocrsend --strictcrlpolicy --nat_traversal --keep_alive - > 230 ? S 0:00 logger -p daemon.error -t ipsec__plutorun > 234 ? S 0:00 /bin/sh /usr/local/lib/ipsec/_plutorun --debug none > --uniqueids yes --nocrsend --strictcrlpolicy --nat_traversal --keep_alive - > 235 ? S 0:00 /bin/sh /usr/local/lib/ipsec/_plutoload --load %search > --start %search --wait --post > 239 ? S 0:00 /usr/local/lib/ipsec/pluto --nofork --debug-none --uniqueids This is a normal collection of the threads you'd see when FreeS/WAN is running. > But then if I restart it, I am notified that IPSec wasn't running. Why > and how? If there's been some sort of crash, it will be reported in your logs. Do you see any reports of a failure? (hint: ipsec barf) - -- Sam Sgro [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv Comment: For the matching public key, finger the Reply-To: address. iQCVAwUBPy3/sUOSC4btEQUtAQE7xgP/bhQYyLvGgkgnw6IB42+Q5HlRgR/tM36W 7Jc6V/joPJ0vqQPcarLMu8bzOfm2drYfRD1/Qyfj1F6Bh8289+ANScL6sOPCZ/mt 9nUHFYNHI91hwMnjO4HWGTGYBdsDh7hYa6fWk0fgIIjTZfMdM4HWuhvnTtE22hiF ZjJCTiIu+y8= =wzk4 -----END PGP SIGNATURE-----
