Path: utzoo!utgpu!watmath!clyde!att!pacbell!ames!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: ucdavis!sunny!poage@ucbvax.berkeley.edu (Tom Poage)
Newsgroups: comp.sys.sun
Subject: Re: SunOS 3.2 tip problems
Message-ID: <347@sunny.UUCP>
Date: 4 Dec 88 03:04:20 GMT
References: <8811140237.AA05436@gmu90x.gmu.edu>
Sender: usenet@rice.edu
Organization: Rice University, Houston, Texas
Lines: 29
Approved: Sun-Spots@rice.edu
Original-Date: 23 Nov 88 05:04:01 GMT
X-Sun-Spots-Digest: Volume 7, Issue 37, message 3 of 12

J Dana Eckart writes:
>X-Sun-Spots-Digest: Volume 7, Issue 23, message 3 of 12
>
>I have a Sun 2 running SunOS 3.2, my problem is that tip leaves a
>LCK..cua0 file in /usr/spool/uucp after "normal" users finishing
>"tip"ping. If root runs tip, however, the offending file is removed
>automatically.  I also have the problem that tip won't disconnect when the
>other modem drops the connection.
>...

Try this,

Problem:	Normal user uses tip(1).  Tip leaves lockfile LCK..*
		in /usr/spool/uucp.  Lockfile does *not* go away.
		However, lockfile *does* go away for root and uucp.

Solution:	1) Make new group uucp in /etc/group.
			uucp:*:4:user,user, . . .
		2) Chown uucp.uucp /usr/bin/tip
		3) Chmod 04750 /usr/bin/tip
		4) Chown -R uucp.uucp /usr/spool/uucp
		5) Chmod 0775 /usr/spool/uucp

The lockfile goes away when it's supposed to, security isn't too bad(?),
and those not in the uucp group can't access tip.

Tom Poage, UCDMC Clinical Engineering, Sacto., CA
ucdavis.ucdavis.edu!sunny!{poage,root,postmaster,news}
ucbvax!ucdavis!sunny!{poage,root,postmaster,news}