From: SourceForge.net <no...@so...> - 2006-08-29 13:55:16
|
Bugs item #1173819, was opened at 2005-03-30 20:38 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=111118&aid=1173819&group_id=11118 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: unix-specific Group: version 3.0 >Status: Pending Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) >Assigned to: Fabian Keil (fabiankeil) Summary: OpenBSD 3.6 w/ Privoxy 3.0.3 Initial Comment: Seen lots of reports on similar problems. What's happening with me is after about 5 minutes with no warning, Privoxy process just dies. No logs, no nothing that I can find to help pinpoint the cause. Using six action files, all rather large in size. Running Privoxy on Intel PII-233 with 256MB. Logging/debug 512 only. pls contact me @ ogu...@ho... ---------------------------------------------------------------------- >Comment By: Nobody/Anonymous (nobody) Date: 2006-08-29 06:55 Message: Logged In: NO Is this still a problem? Did you use the official build or the OpenBSD port? I recently tested the port on OpenBSD 3.9 without problems. It was just to see if some modifications worked and unrelated to your problem report, but I had it running in the background for more than an hour. The port has additional patches that treat OpenBSD similar to MacOS X when it comes to mutexes. Maybe the official build should do the same, the port's maintainer probably knows best what's good for OpenBSD. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=111118&aid=1173819&group_id=11118 |