sylvain@lvbull.UUCP (Sylvain Langlois RCG-ARS) (02/09/85)
<*****> Since I brought up the news system on my machine, I have this little vicious bug somewhere, but I can't find where it comes from (and I don't really have time to trace it down!). I'm hooked up to the french backbone with 300bds modem on which sits an auto -dialer (guess it has nothing to do with this!). We mostly receive news at night, and almost all the time, the following message is sent back to my news feeder: >> From su "DD" "MM" "dd" "hh:mm:ss" "YY" remote from "my-machine-name" >> uuxqt cmd(rnews ) status (exit 0, signal 139) (Note: quoted strings are components of the date, and seem to be correct). At the same time, it has dumped core and tried to send some mail, but did not succeed and left an empty "dead.letter" in UUCP spool, and it has lost (I guess) as many news articles as the number of this message in the spool. This strange behaviour doesn't occur when I run uuxqt by hand. Where is the bug coming from: rnews, uuxqt, shell? Any idea? I'm running a V7 UN*X system with strong 4.2BSD kernel enhancements. This thing happened before when I was using a "pure" V7 kernel. News sofware has been compiled with the V7 option, and I never recompiled it after I moved to the new kernel. (News is user level-code and I don't think it will change a lot recompiling it, except using some 4.2BSD sys calls - some of which are still not ported!). If anyone could help, he/she is welcome, but take care of duplicating your answer by mail in case I loose the news reply! Thanks a lot. ========== Sylvain UUCP: ...{seismo}!mcvax!vmucnam!lvbull!sylvain