[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon Jun 23 22:02:54 1993 
Subject:Re: Help Needed with ved_postnews 
From:"A.Sloman" 
Volume-ID:930623.04 

James did you ever get an answer to this?

> O.K. Enough, is enough. Can anyone out there help me with this problem
> posting news? System is networked suns.
>
> N.B. reply to me directly (I don't get pop-forum mail any more) or
> post to comp.lang.pop if the answer is interesting enough.
>
> If you don't know what the answer is, perhaps you could suggest how I
> track it down?
>
> -- Error message ------------------------------------------------------
>
> Sussex POPLOG (Version 14.2 Wed Feb  3 12:46:18 GMT 1993)
>
> ** SENDING NEWS. PAUSE IN CASE OF ERROR MESSAGES FROM NEWS HOST.
>
> <<<<<<< Access Violation: PC = 00187774, Addr = 00000008, Code = 3 >>>>>>>
>
>
> ;;; MISHAP - serr: MEMORY ACCESS VIOLATION (see above)
> ;;; DOING    :  applist sendnews do_postnews runproc charin null nextitem
>      compile pop_setpop_compiler


Here are some possible things to explore.

I found that if I sent mail with ved_send_wait false in the context
of a process that had been used with X facilities (e.g. lib
propsheet, lib rc_graphic), I got access violation errors. The cure
was to make ved_send_wait true, which slightly slows things down but
not much on the SPARC systems I use.

You could try the same with ved_postnews. (The problem is a bug that
has been reported to Sussex, and I gather from Adrian Howard that it
has been tracked down and will be fixed in the next Poplog release.)

Another thing to do is replace the call of sysvfork() with
sysfork(). Again that may slightly slow things down but is much
safer, and on Suns the virtual fork system call will eventually
be withdrawn because it is apparently being made redundant by
changes to the fork system call.

I hope that helps. I use ved_postnews often, but the context is
slightly different.

Incidentally I wonder if anyone has tailred ved_gn to cope with
NNTP directly? My version works only via the nntptools package which
is a bit slow, though otherwise it's fine.

Aaron