| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 12:34 Fri 07 Sep , Greg Lindstrom wrote: |
| 5 |
<snip> |
| 6 |
> When I run the file from the command line everything works great, |
| 7 |
> but when I schedule the job to run from the crontab file, the original file |
| 8 |
> is created and populated, but the rename fails. I am using full paths for |
| 9 |
> both the original and destination file, and run the command line version |
| 10 |
> after I 'su' to the production account (named 'edith'). |
| 11 |
<snip> |
| 12 |
|
| 13 |
I think cronjobs have a very limited environment (Reduced $PATH and so on). So |
| 14 |
the first point I would check ist that my application does not depend on any |
| 15 |
environment variables (call all binaries with their full path, for example). |
| 16 |
Then, make sure that the user you are running at has the necessary permissions |
| 17 |
to do so (does'nt seem to be a problem with you). And another thing: The cron |
| 18 |
processes have no controlling terminal, so that's something which may go awry. |
| 19 |
HTH |
| 20 |
Jan Seeger |
| 21 |
-----BEGIN PGP SIGNATURE----- |
| 22 |
Version: GnuPG v1.4.7 (GNU/Linux) |
| 23 |
|
| 24 |
iD8DBQFG477iMmLQdC6jvocRAgGKAJ9iali9yPgTUgz68t/Vn5wf9UHWtgCfTVnJ |
| 25 |
yQmdQd4SmO88bR9W7tIwdD4= |
| 26 |
=WlTn |
| 27 |
-----END PGP SIGNATURE----- |
| 28 |
-- |
| 29 |
gentoo-user@g.o mailing list |
Archives