dce@mips.UUCP (David Elliott) (08/04/87)
After changing kermit to use /usr/spool/locks for lock files,
I found that kermit doesn't run setuid uucp like tip and uucico
do. Thus, it can't create lock files, which causes minor problems.
Does anyone have changes to make C kermit run properly as
setuid uucp? Or, can anyone convince me that it is OK to have
the lock directory publicly writable?
--
David Elliott {decvax,ucbvax,ihnp4}!decwrl!mips!dcebeede@hubcap.UUCP (Mike Beede) (08/19/87)
in article <565@quacky.UUCP>, dce@mips.UUCP (David Elliott) says: > [ stuff about changing kermit's lock directory omitted ] > Does anyone have changes to make C kermit run properly as > setuid uucp? Or, can anyone convince me that it is OK to have > the lock directory publicly writable? > We use Kermit a LOT here, and one thing I've found is that it's very easy for a user to croak Kermit off, requiring the lock file to be manually deleted. Assuming your users are trustworthy, there isn't a problem (at least with us). -- Mike Beede Computer Science Dept. UUCP: . . . !hubcap!beede Clemson University INET: beede@hubcap.clemson.edu Clemson SC 29634-1906 YOUR DIME: (803)656-{2845,3444}