Well well well..... I found the problem... People, it might help if you find out later that your boss has been snooping around the /etc/printcap file and stuffed one of the last printers in the list hence this is what happens: 1. Machine starts up and lpd starts up fine. 2. Print job comes in and lpd spawns a process. 3. Process runs down the printcap list and finds a problem entry. 4. Process gets STUCK in that entry. 5. User sends more data and no jobs get printed. 6. Admin restarts lpd and works fine again due to the child process being killed. 7. lpd starts again and see more jobs and spawn process again until it gets stuck again.. 8. and the beat goes on....... That was why it always worked on first start and restart of lpd but then fails there after. Somehow my boss fscked with the printcap file which I didn't even see that entry and caused me grief.... Oh well, you all know next time... Thanks alot Grahame for those files and your great response... -----Original Message----- From: Grahame Kelly [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 01, 2000 5:31 PM To: George Vieira Subject: RE: [SLUG] LPD is actually stuffed again. On Wed, 01 Nov 2000, you wrote: > Can you give me an example of setting this up urgently. I have a customer > who can't print to 8 of their printers. > I downloaded LPRng3.2.6 and it core dumped on me... > > any help would be appreciated. Well here are my lpr files from /etc. Its pretty simple stuff. The doco is resonable. Cheers, Grahame -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
