From: John H. <jh...@cp...> - 2003-04-15 22:52:38
|
Bill, Mike -- let me make sure I have some things straight: Are you running assp as a backgrounded process (ie perl assp.pl &)? Try inserting this line after the mlog(0,"Starting"); (line 182?) close STDOUT; close STDERR; (One wouldn't want to do this unless $silent = 1) I'm just a little baffled because ASSP uses no pipes. So when you background the process (somebody correct me if I'm wrong) Linux pipes STDOUT to the console, and that would be the only pipe I'm aware of. Another possibility is that there's an internal memory corruption problem within Perl -- the solution to this would be to make ASSP use less ram -- I can do that but it will slow it down. Any other Linux folks out there getting the Broken Pipe error? Thanks, John ----- Original Message ----- From: "Bill Butler" <bi...@bu...> To: <ass...@li...> Sent: Tuesday, April 15, 2003 3:54 PM Subject: Re: [Assp-user] Broken Pipe > I do have $silent=1 uncommented. Here is an excerpt from my config.pl file: > > > $logfile="$base/maillog.txt"; > $silent=1; # silent=1 means don't print log > messages to the console > $pidfile="$base/pid"; > > > At 03:22 PM 4/15/2003 -0600, you wrote: > >Do you guys have $silent=1 uncommented in your config.pl file, or > >(alternatively) are you redirecting STDOUT (and possibly STDERR)? > > -- > Bill Butler > Butler Networks > bi...@bu... > 615-369-7070 > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Assp-user mailing list > Ass...@li... > https://lists.sourceforge.net/lists/listinfo/assp-user > |