cron has minimal environment.
You can simulate it on the command line:
env -i clears the environment, then USER and HOME are set from the current env, and PATH is set to the default, then the command is run.
If you do not use parameters 1 and 2 then you should use 1>/dev/null and 2>&1 (no spaces!) to supress eventual output.
But not for the test on the command line - here you want to see something!
Last edited by rbatte1; 07-22-2019 at 08:14 AM..
Reason: Correcting end CODE tag marker
Hello All,
I m newbie to Job scheduling.
Suppose i have 2 files s1.sh and s2.sh i want to make a schedule such as
run s1.sh at 2AM everyday and run s2.sh 9Pm everyday.
Can anyone tell me how to schdule that using CRON and i want to know what is CRON and CRONTAB.
Thanks in advance (2 Replies)
Hi,
from normal user(oracle) i am unable to run scheduled job in cron:
os version:
bash-2.03$ uname -a
SunOS sumail02 5.8 Generic_117350-39 sun4u sparc SUNW,Ultra-60
bash-2.03$ crontab -l
55 * * * * sh /oracle/statistics.sh > /dev/null 2>&1
bash-2.03$ cat /oracle/statistics.sh... (2 Replies)
Hi,
I want to run cron scheduler to run some script at different times of the day.But these times don't have some fix intervals. So how we can run jobs at 6:30AM, 1:00PM and 4:30PM everyday.
Please help.
Thanks
Neeraj (2 Replies)
Hi all,
I am new to cron jobs..
i wanted to schedule a cron job that wil send a mail to me at 3:00PM on 10th August ie is on Wednesday.
0 15 10 8 3 echo "message from UNIX here"|mail -s "your subject here" user@user.com
However this was not executed...
Can anyone please... (0 Replies)
Hi,
Can anyone help me out with scheduling a cron job for the below:
i wnated to delete file from a folder on every sunday at 05:00 AM
this is code i have used.
*******************************************************
0 05 * * 0 find /abc/xyz/pqrs/bak/ -type f -mtime +30 -exec rm -f... (5 Replies)
Please guide me how to schedule the cron job to run on every Saturday at 6am with the interval of 21 days. (2 Replies)
Discussion started by: raghavendrajsv
2 Replies
LEARN ABOUT OPENDARWIN
printenv
PRINTENV(1) BSD General Commands Manual PRINTENV(1)NAME
printenv, env -- print out the environment, set and print environment
SYNOPSIS
printenv [name]
env [-i] [name=value ...] [utility [argument ...]]
DESCRIPTION
The printenv utility prints out the names and values of the variables in the environment, with one name/value pair per line. If name is
specified, only its value is printed.
Some shells may provide a builtin printenv command which is similar or identical to this utility. Consult the builtin(1) manual page.
The env utility executes utility after modifying the environment as specified on the command line. The option name=value specifies an envi-
ronment variable, name, with a value of value.
The options are as follows:
-i Execute the utility with only those environment values specified. The environment inherited by env is ignored completely.
If no utility is specified, env prints out the names and values of the variables in the environment, with one name/value pair per line.
The env utility is sometimes useful with the ``#!'' construct (see execve(2)). The only difference between ``#!/usr/local/bin/foo'' and
``#!/usr/bin/env /usr/local/bin/foo'' is that the latter works even if /usr/local/bin/foo is itself interpreted. Using env this way also
allows one to reference foo without the path, as well as set up the environment as desired.
ENVIRONMENT
The env utility uses the PATH environment variable is used to locate the requested utility if the name contains no '/' characters.
DIAGNOSTICS
The printenv utility exits 0 on success, and >0 if an error occurs.
The env utility exits 0 on success, and >0 if an error occurs. An exit status of 126 indicates utility was found, but could not be executed.
An exit status of 127 indicates utility could not be found.
COMPATIBILITY
The env utility accepts the - option as a synonym for -i.
SEE ALSO csh(1), sh(1), execvp(3), environ(7)STANDARDS
The env utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
HISTORY
The printenv command appeared in 3.0BSD.
BUGS
The env utility doesn't handle utility arguments with equal (``='') signs in their names, for obvious reasons.
BSD June 6, 1993 BSD