Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/3/84; site maynard.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!wjh12!maynard!campbell
From: campbell@maynard.UUCP (Larry Campbell)
Newsgroups: net.unix-wizards
Subject: Re: Running C programs with cron ???
Message-ID: <163@maynard.UUCP>
Date: Thu, 26-Sep-85 22:02:49 EDT
Article-I.D.: maynard.163
Posted: Thu Sep 26 22:02:49 1985
Date-Received: Sat, 28-Sep-85 07:46:44 EDT
References: <21900005@orstcs.UUCP>
Organization: The Boston Software Works Inc., Maynard, MA
Lines: 20

> Has anyone experienced problems with the 'system()' call within a C
> program not being executed properly when the program is executed via
> cron?  ...

Your problem may be that in some Unix implementations, the first thing
cron does is

	setuid(1);

which means it (and its children) probably doesn't have permission to
write in any log files you might be trying to use to leave tracks.
I've found that removing the setuid makes cron much more useful.
-- 
Larry Campbell                     decvax!genrad
The Boston Software Works, Inc.                 \
120 Fulton St.                 seismo!harvard!wjh12!maynard!campbell
Boston MA 02109                         /       /
                                   ihnp4  cbosgd

ARPA: campbell%maynard.uucp@harvard.arpa