01-29-2008
I have a bit of time now so lets explain:
> < root 14906 c Fri Jan 11 00:34:00 EST 2008 rc=127
> The test file was not updated
rc=127 -> You have a problem can be : cannot fork, or return code from your shell
Start by checking you have a correct and all your program needs in your path! because there is big chance all its missing is that ( and so the error should be understood as:cant do because not found...)
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
HI,
I need to schedule a no.of jobs using the cron facility.
I currently do two kinds of scheduling,one based on the database load(after the database is loaded the program will start) and the other is based on time.....(say 10.00a.m daily)
the problem is..........
When the database is loaded... (1 Reply)
Discussion started by: sireesha15
1 Replies
2. Shell Programming and Scripting
the follwing script is running fine , when run from the ksh shell...it runs properly i.e. waits for a file "test.flag" and sends mail accordingly.
But when I schedule it in the crontab ...it does not run at the specified time (it never runs).
I am using ksh
####shell script starts
count=1... (4 Replies)
Discussion started by: ace@123
4 Replies
3. Shell Programming and Scripting
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)
Discussion started by: prakash.gr
2 Replies
4. UNIX for Dummies Questions & Answers
I have cron scheduing that after hotbackup omniback kicks in and back up tape.
00 17 * * * /usr/local/bin/archbakPRD/mainPRDbackup.sh > /usr/local/bin/archbakPRD/dbfcopy.log 2 >&1
above cron can fired every night at 5PM but omnibackup need to have seperate name for each backup ( i.e:... (1 Reply)
Discussion started by: Paul.S
1 Replies
5. Solaris
Hi ,
I am trying to set up a cron job for getting the prstats for every 10 minutes to a log file.
prstat -s cpu -n 20 > a.txt
The issue is when i try to execute this command, a.txt is filling up with data for every second which is not i wanted.I just need top 20 processes for every 10... (2 Replies)
Discussion started by: pyaranoid
2 Replies
6. Shell Programming and Scripting
Hi,
How to write the recursive function.
I have a script,
#!/usr/bin/ksh
##
name=$1
outputfile='output.log'
sqlplus -s > ${outputfile} <<__END__
${USER}/${PASS}@${DB}
WHENEVER SQLERROR EXIT SQL.SQLCODE ROLLBACK
WHENEVER OSERROR EXIT FAILURE ROLLBACK
SET ECHO ON
SET SERVEROUTPUT... (3 Replies)
Discussion started by: sandy1028
3 Replies
7. Shell Programming and Scripting
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)
Discussion started by: ch33ry
0 Replies
8. UNIX for Dummies Questions & Answers
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)
Discussion started by: ch33ry
5 Replies
9. Shell Programming and Scripting
Hi All,
Is there any way (any utility) to schedule a job to run once in a week on RedHat Linux ?
Note- Do not using Crontab.
Thanks
Pravin (1 Reply)
Discussion started by: pravin27
1 Replies
10. HP-UX
Hope you can help with a queuy i have. Server OS is HP-UX
my cron runs like this:
* * * * * /test/scripts/1_min_jobs.sh 1>/dev/null 2>/dev/null
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /test/scripts/jobs_5mins.sh 1>/dev/null 2>/dev/null
0,15,30,45 * * * *... (10 Replies)
Discussion started by: davexxash
10 Replies
SYSTEM(3) Linux Programmer's Manual SYSTEM(3)
NAME
system - execute a shell command
SYNOPSIS
#include <stdlib.h>
int system(const char *command);
DESCRIPTION
system() executes a command specified in command by calling /bin/sh -c command, and returns after the command has been completed. During
execution of the command, SIGCHLD will be blocked, and SIGINT and SIGQUIT will be ignored.
RETURN VALUE
The value returned is -1 on error (e.g. fork(2) failed), and the return status of the command otherwise. This latter return status is in
the format specified in wait(2). Thus, the exit code of the command will be WEXITSTATUS(status). In case /bin/sh could not be executed,
the exit status will be that of a command that does exit(127).
If the value of command is NULL, system() returns nonzero if the shell is available, and zero if not.
system() does not affect the wait status of any other children.
CONFORMING TO
C89, C99, POSIX.1-2001.
NOTES
If the _XOPEN_SOURCE feature test macro is defined, then the macros described in wait(2) (WEXITSTATUS(), etc.) are made available when
including <stdlib.h>.
As mentioned, system() ignores SIGINT and SIGQUIT. This may make programs that call it from a loop uninterruptible, unless they take care
themselves to check the exit status of the child. E.g.
while (something) {
int ret = system("foo");
if (WIFSIGNALED(ret) &&
(WTERMSIG(ret) == SIGINT || WTERMSIG(ret) == SIGQUIT))
break;
}
Do not use system() from a program with set-user-ID or set-group-ID privileges, because strange values for some environment variables might
be used to subvert system integrity. Use the exec(3) family of functions instead, but not execlp(3) or execvp(3). system() will not, in
fact, work properly from programs with set-user-ID or set-group-ID privileges on systems on which /bin/sh is bash version 2, since bash 2
drops privileges on startup. (Debian uses a modified bash which does not do this when invoked as sh.)
In versions of glibc before 2.1.3, the check for the availability of /bin/sh was not actually performed if command was NULL; instead it was
always assumed to be available, and system() always returned 1 in this case. Since glibc 2.1.3, this check is performed because, even
though POSIX.1-2001 requires a conforming implementation to provide a shell, that shell may not be available or executable if the calling
program has previously called chroot(2) (which is not specified by POSIX.1-2001).
It is possible for the shell command to return 127, so that code is not a sure indication that the execve(2) call failed.
SEE ALSO
sh(1), signal(2), wait(2), exec(3)
COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
2004-12-20 SYSTEM(3)