2012/11/23 Anton Aylward :

Meike Stone said the following on 11/23/2012 10:59 AM:

...

2012/11/23 Anton Aylward :

...

Joachim Schrod said the following on 11/23/2012 10:49 AM:

...

I use Perl to test that the env var is set for all cron jobs and not just for shell scripts.

If you used the 'env' command you'd see a lot more and that _might_ give a clue.

I tried 'env' and 'set' in the crontab, but the variables are not set ...

That's not what I meant I'm talking about the 'env' command not the ENV directive in cron

try 'man 1 env' to see what the env COMMAND does.

If you're not setting the environment then it reports it. That was what I intended

And entry like: * * * * * env

Yes, thats what I mean this too. And I don't want execute any command (via env). I used 'env' to show me the Environment. (from manualpage: "If no COMMAND, print the resulting environment.") I used 'set' and 'env' in my testcron to print out the environment ... Meike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org