From owner-freebsd-current Wed Jul 11 17:32:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 8CE8C37B403; Wed, 11 Jul 2001 17:32:08 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f6C0W7405352; Wed, 11 Jul 2001 20:32:07 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20010711214311.C2855@heechee.tobez.org> References: <873d83pquy.wl@wilhelm.noname> <20010711214311.C2855@heechee.tobez.org> Date: Wed, 11 Jul 2001 20:32:04 -0400 To: Anton Berezin From: Garance A Drosihn Subject: Re: cannot print to remote printer Cc: current@FreeBSD.org, freebsd-print@bostonradio.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 9:43 PM +0200 7/11/01, Anton Berezin wrote: > At 2:55 PM +0200 7/11/01, Georg-W. Koltermann wrote: > > With current as of June 20 I can no longer print to a remote > > printer. Syslog says "filter 'f' exited (retcode=108)". > > > > I added a "set -x" to the filter which is a shell program, and > > sure enough the last action it does is an "exit 0". So the problem > > must be somewhere in lpd. > >I could reproduce your problem. The following patch appears to solve >it for me: > >Index: lpd.c >=================================================================== >RCS file: /home/ncvs/src/usr.sbin/lpr/lpd/lpd.c,v >retrieving revision 1.26 >diff -u -r1.26 lpd.c >--- lpd.c 2001/06/25 01:45:25 1.26 >+++ lpd.c 2001/07/11 19:35:11 >@@ -367,7 +367,7 @@ > continue; > } > if (fork() == 0) { >- signal(SIGCHLD, SIG_IGN); >+ signal(SIGCHLD, SIG_DFL); > signal(SIGHUP, SIG_IGN); > signal(SIGINT, SIG_IGN); > signal(SIGQUIT, SIG_IGN); I had to make this same change to lpr at RPI to get "things" to work right on some other (non-freebsd) platform, though I did it so long ago that I don't remember what the problem was. I have some other signal-related changes in RPI's version that I intend to merge into freebsd too, but I'll put this change into freebsd-current by itself. I have wondered why I needed that on other platforms but freebsd didn't seem to need it... Thanks! -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message