Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!mit-eddie!bbn!rochester!ritcv!cci632!ccicpg!turnkey!jack From: jack@turnkey.TCC.COM (Jack F. Vogel) Newsgroups: comp.unix.xenix Subject: Re: SCO Xenix 2.2.1 lp problem Message-ID: <212@turnkey.TCC.COM> Date: 4 Jun 88 17:46:38 GMT References: <22@libove.UUCP> <552@wsccs.UUCP> <5035@june.cs.washington.edu> Reply-To: jack@turnkey.TCC.COM (Jack F. Vogel) Distribution: comp Organization: Turnkey Computer Consultants, Costa Mesa, CA Lines: 26 In article <5035@june.cs.washington.edu> kevinr@uw-june.UUCP (Kevin Ross) writes: >In article <22@libove.UUCP>, root@libove.UUCP (The Super User) writes: >> I have a problem somewhere in that with the line printer stuff. >> I can't get the scheduler running. > >One thing you might want to try is starting the scheduler manually. I have >had a similar problem from time to time. I thought I had answered this question before, but perhaps that was a different instance. lpsched should be started at boot time when /etc/rc is run. If it is not then (assuming you have not mucked with the rc file) there is some problem with the spool system and chances are that invoking it manually will not solve the problem. The solution is simple, when lpsched fails at boot it will report the problem in /usr/spool/lp/log. Simply go read that file and it should reveal what the problem is, possibly a missing spool, member, or request directory, etc. Fix the problem, and then call lpsched manually, if need be go back and check the log again, and so on. Best regards, -- Jack F. Vogel Turnkey Computer Consultants, Costa Mesa, CA UUCP: ...{nosc|uunet}!turnkey!jack Internet: jack@turnkey.TCC.COM