Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!ucsd!nosc!crash!jagat!rwhite
From: rwhite@jagat.uucp (Robert White)
Newsgroups: comp.unix.sysv386
Subject: Re: SCO License security - another flame
Message-ID: <1991Jun4.032557.9455@jagat.uucp>
Date: 4 Jun 91 03:25:57 GMT
References: <1251@dms.UUCP> <1991May23.235200.9371@kithrup.COM> <1991Jun3.062531.17668@hawkmoon.MN.ORG>
Organization: My House (no organization to speak of)
Lines: 20

It is completely effective to su to another accoutn and use
crontab to set the crontab entry into place for that
(su(ed) account) but keep in mind the following:

Crontab uses the user environment to determine who to set
the cron-table for.

If you "su news; crontab newtable" you will be setting the
cron-table for the original logname, not news.

The correct method is to "su - news; crontab newtable"
so that the all-important    ^  setup user environment
features take effect!  If in doubt, try "crontab -l"
on your system after su(ing) to check which table you
will be altering.
-- 
Robert C. White Jr.          |  If you sent me mail and it bounced going
rwhite@jagat           <Home |  through nusdhub, please re-send it if it
rwhite@nusdecs         <Work |  was important.  Implementation Details!
"Like most endevors, life is seriously over-advertised and under-funded"