fsck and printing queue

[Kent Sandvik]

HEPING at kuhub.cc.ukans.edu writes in article <19680 at kuhub.cc.ukans.edu>:
      When I used fsck to check the file system, I got the following error msg:
      
      POSSIBLE FILE SIZE ERROR  I = 1767
      POSSIBLE FILE SIZE ERROR  I = 3295
      
      LINK COUNT TABLE OVERFLOW
      CONTINUE?
      
      In the manul "A/UX Local System Administration", it says "This is a rare
      error". But it doesn't say how to fix it. Can some one help me?

The fsck program has an internal table for a list of allocated inodes
with a link count of zero.  If this fsck table overflows when using
fsck, it generates the error above. 

If the administrator continues with fsck, the program will not do a
complete check of the system, so the best thing is to rerun fsck once
more after this message. 

      
      The second problem I have is that I will get some printing files in my system
      after I run A/UX 1.1 for a while even through I have no priter connected on
      my network. When I use ' lpstat -o ' to print the status of all output
      requests,
      I get something like this:
      
      	...
      	laser-289    	lp	5123  Dec 12 12:03
      	laser-290 	lp 	39873 Dec 12  2:34
 
This needs some detective work; check the /usr/spool/lp/log for any more
information what is going on, and check the spooled files under
/usr/spool/lp/request/laser in order to understand what is sent out. 


/Kent
-- 
Kent Sandvik  --  ksand at appleoz.oz.AU  | Apple Australia DTS  Ph: +61 2 452 82 93
{uunet,mcvax}!munnari!appleoz.oz!ksand | AppleLink: AUSTAUX, Discl: All comments mine
-- CyberSpace, the Final Frontier --