CRON problem using script...

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Execution problem with Cron: Script works manually but not w/Cron. Why?

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...

2. Shell Programming and Scripting

Please help me in cron problem

When i am working with cron i given the command as crontab - e | grep runjob.sh.I though my command is wrong and i closed it by ctrl+D.After that when i need to open the cron with crontab -e its not opening its giving some number 22667 and when i given crontab -l its working fine i can see all...

3. UNIX for Dummies Questions & Answers

Problem automating sFTP transfer using script in cron

Hi Newbie here I am having problems with automating sFTP transfers. Just to save time - SCP is not an option as sFTP is stipulated by controllers of far end server. Ineed to automate sFTP transfer of a single file, once a day to a remote server to which i have no control over. I am using:...

4. Shell Programming and Scripting

Problem with executing a shell script through the cron

Hi, I have a shell script as below: ORACLE_HOME=/usr/local/opt/oracle/product/dev export ORACLE_HOME PATH=$PATH:$ORACLE_HOME/bin:/usr/bin export PATH OUTFILE=/export/home/`basename $0`.out export OUTFILE export IDEN df -k . | tail -1 | read a b c d e f echo $a >> $OUTFILE echo $b...

5. UNIX for Dummies Questions & Answers

Problem with scheduling a shell script on cygwin using cron

Hi, Before I start, I would like to inform that, I went through all FAQs and other threads before posting here. I 'm trying to schedule a shell script on cygwin using cron. No matter what I do I don't seem to get the cron job executing my bash script. My script is temp.sh echo `date` >...

6. UNIX for Dummies Questions & Answers

problem when the script is scheduled to run as cron job

Hello, I have problem in executing a shell script. When the shell script is executed at the shell prompt the script works successfully but when the same script is run as a cron job it fails to execute the files called within the shell script. I have scheduled the job in my crontab file as ...

7. Shell Programming and Scripting

script execute by cron problem, but manual ok

Hi; I'm facing the problem with my script like below 30 0 * * * /data/SCRIPT/LOADLOGS/loadata1.sh 2 1 >> /tmp/loaddata.txt loadata1.sh calling a another 2 scripts which we need to exe in sequence. when it perform by cron jon, sometimes it just can process 20 recs or less or nothing but...

8. AIX

problem with a script and the cron

hello I use a script to give me the number of users, at each hour. this script read a file where there is the number of users for each hour and for each month (so 12 files per year). If i execute the script (root), it is ok, i have xxx users for each hour. if I put the script in the cron...

9. Shell Programming and Scripting

Cron Problem

Hello All, One of my shell scripts was working fine till a few days back. It was scheduled in the cron. But yesterday i made some modifications to the script. The script works fine when i run it from the prompt. But it is not working when in runs from cron. Can someone help me out from this.

10. Shell Programming and Scripting

cron job problem with csh script

I've written a csh shell script to number each line of a file. Firstly, the program count the number of the file and create a file with number at the front. Then, combine the file together. when i call the program manually, it works.However, when i set it in the cronjob, the output always leaves...

LEARN ABOUT BSD

kill

KILL(1) 						      General Commands Manual							   KILL(1)

NAME

       kill - terminate a process with extreme prejudice

SYNOPSIS

       kill [ -sig ] processid ...
       kill -l

DESCRIPTION

       Kill  sends the TERM (terminate, 15) signal to the specified processes.	If a signal name or number preceded by `-' is given as first argu-
       ment, that signal is sent instead of terminate (see sigvec(2)).	 The  signal  names  are  listed  by  `kill  -l',  and	are  as  given	in
       /usr/include/signal.h, stripped of the common SIG prefix.

       The  terminate  signal  will  kill  processes  that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be
       caught.	By convention, if process number 0 is specified, all members in the process group  (i.e.  processes  resulting	from  the  current
       login)  are  signaled  (but  beware:  this works only if you use sh(1); not if you use csh(1).)	Negative process numbers also have special
       meanings; see kill(2) for details.

       The killed processes must belong to the current user unless he is the super-user.

       The process number of an asynchronous process started with `&' is reported by the shell.  Process numbers can also be found by using ps(1).
       Kill  is  a  built-in  to  csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill
       arguments.  See csh(1) for details.

SEE ALSO

       csh(1), ps(1), kill(2), sigvec(2)

BUGS

       A replacement for ``kill 0'' for csh(1) users should be provided.

4th Berkeley Distribution					  April 20, 1986							   KILL(1)

Shell Programming and Scripting