Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!mips!mips!sdd.hp.com!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!ira.uka.de!math.fu-berlin.de!unidui!du9ds3!veit From: veit@du9ds3.uni-duisburg.de (Holger Veit) Subject: Re: 2 Problems: No disk Label, Tip doesn't Work References: <1992Jul27.152614.25898@psg.com> <1992Jul28.065521.3441@spcvxb.spc.edu> <1992Jul28.122647.7234@ulowell.ulowell.edu> <Bs3wJp.88I@watdragon.uwaterloo.ca> Date: 29 Jul 92 08:24:24 GMT Reply-To: veit@du9ds3.uni-duisburg.de Organization: Uni-Duisburg FB9 Datenverarbeitung Sender: @unidui.uni-duisburg.de Message-ID: <veit.712398264@du9ds3> Lines: 37 In <Bs3wJp.88I@watdragon.uwaterloo.ca> kcwellsc@watdragon.uwaterloo.ca (Ken Wellsch) writes: >> The second problem I had was getting tip to work, and I saw a >> couple of posts about this, but no solution. When tip is configured >> properly, we get the >> no file or no lock error. (sorry, I can't be more precise, but >> I can't get that far again without reinstalling 386BSD on my whole >> system, and then I can't get tip to work to read mail and news for the >> solution :-) >I think you will find that "tip" is setuid "uucp." Now it wants to create >a lock file under /var/spool/lock I believe. You'll probably find that >/var/spool/lock is owned by root and mode 0755. Thus "uucp" is unable to >write/create a lock. I'm not sure whether "uucp" should own the directory >or if it should be world writeable with the sticky-bit on like /tmp. I looked at SunOS to see what they did. They have -rws--x--x 1 acu daemon 73728 Feb 8 1990 /usr/bin/tip and drwxr-sr-x 13 bin bin 512 Jul 25 11:31 /var/spool drwxr-sr-x 2 acu uucp 512 Jul 23 18:03 /var/spool/locks This looks quite reasonable. Look if something like this works under 386bsd (perhaps replace acu with uucp, or create an entry). Hope that helps. Holger -- | | / Holger Veit | INTERNET: veit@du9ds3.uni-duisburg.de |__| / University of Duisburg | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO | | / Dept. of Electr. Eng. | "No, my programs are not BUGGY, these are | |/ Inst. f. Dataprocessing | just unexpected FEATURES"