Yes: the same way you use it in other scripts, but cronjobs inherit nothing from their parent process (unlike jobs started from an interactive shell).
For this reason i do NOT rely in my scripts on a set environment at all but set it to a "standard-environment" with a function i source in first:
In short: replace the your job with a script in which a proper environment (including your missing variable) can be set and used easily. Call this script from cron.
Hi,
I want to run my shrip for every 30 min..
if i enter crontab -l i am getting following..
00,10,20,30,40,50 * * * * /home/arbuser/temp2/perform/per.sh
00,15,40,35,50 * * * * sh home/arbuser/temp2/perform/per.sh
if I enter like this :
ps -ef |grep cron
root 311454 1 0... (3 Replies)
I am having a problem running a shell within CRON. It will run successfully if I do not inject a .profile into the entry. However, the second I place a . profile in front of the shell, the job does not execute. Any ideas? (4 Replies)
The cron daemon on one of my HP boxes is giving the following error:
I checked the queuedefs man page, and it has left me a bit confused. The man page says:
So this means that no more than 100 cronjobs can be run at one time (we do not use at and batch on this system).
The... (4 Replies)
Hi,
I've just done a school boy error.
I was trying to edit the crontab but instead of using:
crontab -e
I used crontab -r without realising. Then went to look at the crontab but ntohing their. Looked int he manual and -r removed the crontab.
Is their any way of getting this back??
... (3 Replies)
Hi frnds...
I m facing very irritating problem already waisted my 2 days..
I have a following script..( i am pasting only the main code)
ftp -ivn 213.194.40.77 <<FTP
user $user $password
binary
cd $FileDir/out
lcd $localpath
get $file
rename $FileDir/out/$file $FileDir/tmp/$file... (7 Replies)
I'm using Red Hat and I need to get cron working and I'm not sure what the problem is. As a test I've done the following:
1) In /etc/cron.d I've created a file called date with the following contents
2) */1 * * * * root date >> /root/thedate
3) This works perfectly. It sends the date every... (1 Reply)
Hello folks,
I've got a few cron jobs listed under a particular user id. They are running fine but then they are creating a new process every time they are running. Any idea folks? (3 Replies)
Hi i am new here and have a quick question.
i am receiving ./project.sh: line 12: syntax error near unexpected token `newline'
./project.sh: line 12: `echo "`date +"%F %R"` `md5sum /etc/passwd`" >> '
error message
here is my script. could you please help!
#!/bin/bash
# PROGRAM:... (4 Replies)
Just wanted to know, what happens if a user exists in both files cron.allow and cron.deny.
Will the user be able to set cron?
Thanks,
Deepak (7 Replies)
Hello gurus,
I am making what I think is a simple db2 call from within a shell script but I am having difficulty producing the desired
report when I run the script shown below from a shell script in cron. For example, my script and the crontab file setup
is shown below:
#!/bin/ksh
db2... (3 Replies)
Discussion started by: okonita
3 Replies
LEARN ABOUT OSF1
bg
bg(1) General Commands Manual bg(1)NAME
bg - Runs jobs in the background
SYNOPSIS
bg [job_id...]
Note
The C shell has a built-in version of the bg command. If you are using the C shell, and want to guarantee that you are using the command
described here, you must specify the full path /usr/bin/bg. See the csh(1) reference page for a description of the built-in command.
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
bg: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
None
OPERANDS
Specifies the job to be resumed as a background job. If no job_id operand is given, the most recently suspended job is used. The format of
job_id is described in the Jobs section of the ksh(1) reference page.
DESCRIPTION
If job control is enabled (see the description of set -m in the ksh(1) reference page), the bg utility resumes suspended jobs from the cur-
rent environment by running them as background jobs. If the job specified by job_id is a job already running in the background, the bg
utility has no effect and will exit successfully.
Using bg to place a job into the background causes its process ID to become "known in the current shell execution environment", as if it
had been started as an asynchronous list. See the Jobs section of the ksh(1) reference page.
RESTRICTIONS
If job control is disabled, the bg utility exits with an error and no job is placed in the background. The bg utility does not work as
expected when it is operating in its own utility execution environment because that environment has no suspended jobs.
EXIT STATUS
The following exit values are returned: Successful completion. An error occurred.
ENVIRONMENT VARIABLES
The following environment variables affect the execution of bg: Provides a default value for the internationalization variables that are
unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari-
ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value,
overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes
of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale used to
affect the format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the
processing of LC_MESSAGES.
SEE ALSO
Commands: csh(1), fg(1), jobs(1), kill(1), ksh(1), Bourne shell sh(1b), POSIX shell sh(1p), wait(1)
Standards: standards(5)bg(1)