Xref: utzoo comp.unix.questions:20978 comp.sys.sequent:531
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!mcsun!ukc!pyrltd!jimmy
From: jimmy@pyrltd.UUCP (Jimmy Aitken)
Newsgroups: comp.unix.questions,comp.sys.sequent
Subject: Re: Allowing users to remove files in /usr/spool/at
Message-ID: <1748@pyrltd.UUCP>
Date: 28 Mar 90 09:24:01 GMT
References: <2409@syma.sussex.ac.uk>
Reply-To: jimmy@pyrltd.UUCP (Jimmy Aitken)
Organization: Pyramid Technology Ltd, Farnborough, ENGLAND
Lines: 24
Summary:
Expires:
Sender:
Followup-To:

In article <2409@syma.sussex.ac.uk> andy@syma.sussex.ac.uk (Andy Clews) writes:
>I work on a Sequent Symmetry S81 running DYNIX 3.0.15. My question
>could, however, apply to any UN*X box.
>
>Files in this directory are owned and writeable by the people who gave
>the corresponding "at" command, but because /usr/spool/at can only at
>present be written by root, users cannot delete their own "at" files.
>
>Can anyone suggest a way in which I can give this sort of access to
>/usr/spool/at without compromising system security by allowing the world
>to write to it? I'm a bit wary of creating a setuid'd program to do it.

The way that I 'delete' at jobs when I don't want them to run is by
truncating the file.  The easiest way to do this is to:
echo > /usr/spool/at/<whatever>  for csh and sh
or
> /usr/spool/at/<whatever> for sh

Jimmy
-- 
      -m-------  Jimmy Aitken                ...!mcvax!ukc!pyrltd!jimmy
    ---mmm-----  Pyramid Technology Ltd      jimmy@pyra.co.uk
  -----mmmmm---  Pyramid House, Solartron Rd jimmy@pyramid.pyramid.com
-------mmmmmmm-  Hants GU14 7PL, ENGLAND     (+44) 252 373035