I am worried about the standard going offline procedures when we still are fetching and want to hang up the phone even though there is lots more to fetch.
If all works as it should, then after hanging up there should be lots of stuff still in 'outgoing'. However isn't there a race condition involved in just relying on poff and its scripts? That the connection is severed, wwwoffle gets Domain Not Found for lots of files in outgoing, and only then is wwwoffle told to go offline... Therefore one needs to alias byebye='wwwoffle -offline; poff' it seems. This theoretically just leaves the 7 or 8 files that are actually being fetched at the time to worry about, eh? Anyways, have I shown that putting wwwoffle -offline in say /etc/ppp/ip-down.d/99wwwoffle is just plain wrong? Or maybe it because I use wwwoffle<->privoxy<->internet and wwwoffle would know that not getting to the DNS is not a 404 but privoxy cant tell wwwoffle that in a polite way... anyway so maybe my byebye alias will cure this, except for the 7 or 8 currently being fetched files... wwwoffle -offline doesn't stop those in their various tracks... BTW, Tons of these pairs were seen on those bad occasions: Feb 1 05:39:54 debian wwwoffles[2297]: Spooled Reply Head (from cache) is empty. Feb 1 05:39:54 debian wwwoffles[2297]: Outgoing Reply Head (to browser) is empty. -- http://jidanni.org/ Taiwan(04)25854780
