Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: cron job error
Top Forums Shell Programming and Scripting cron job error Post 302325644 by aemunathan on Monday 15th of June 2009 10:38:24 PM
Old 06-15-2009
Hi

I found the error but correction needs some help...
in the MSISDNcdrcount script file i have used the filename derived from the date command..it works fine when am running the script from the path where these files are available. But when i do it through cron the complete file path is required where the files are available

thats y it throws error.

i tried like this afterwards
Code:
#!/bin/ksh
filename=`TZ=CST+24 date +%Y%m%d`
#filepath=/space/canvas/home/lbs/current/internalcdrbackup/LES_CDR_Configuration/0/
b=`TZ=CST+24 date +%d-%b-%Y`
host=$(hostname)
/usr/xpg4/bin/awk -v file="$filename" -v serv="BSNLSERVICE1" -v val="2128" -v da="$b" -v ho="$host" '
$4==serv && $6==val {
  b[$9]++
}
END{
  for (i in b )
  { print da, i, b[i],ho }
}' $(/space/canvas/home/lbs/current/internalcdrbackup/LES_CDR_Configuration/0/$filename*)

am not successful in assigning the filename alongwith path.
can any one suggest me the way to assign filename alongwith path in the scriptfile.

-----Post Update-----

hi
got it...used the filename like this
Code:
/space/canvas/home/lbs/current/internalcdrbackup/LES_CDR_Configuration/0/$filename*

 

10 More Discussions You Might Find Interesting

1. Solaris

cron job starts new cron proccess

I run cron in solaris 10 zone. One cron job which syncing files to nfs mounted on container, creates after finishing another cron proccess(/usr/sbin/cron), and after 100 existing cron proccesses next cron job will not start. It's too weird for me, I'm not able to solve this problem. Theoretically... (3 Replies)
Discussion started by: ron76
3 Replies

2. Shell Programming and Scripting

Cron job giving error while running SSH command

Hi All, The script which i am using to SSH to remote server is working fine when i run is using ./ but when cron runs it it gives error that "ssh: not found" please help!!! (3 Replies)
Discussion started by: visingha
3 Replies

3. UNIX for Dummies Questions & Answers

Error in cron job;

Hi All, please help me out with this problem. While running my mail_out_original.ksh in CRT window, it disconnects from the server saying not connected Here is my code : (please see the attachment) ____________________________________________________________ #!/bin/ksh ## Load... (1 Reply)
Discussion started by: shruthinagaraj
1 Replies

4. Shell Programming and Scripting

Error in cron job;

Hi All, please help me out with this problem. While running my mail_out_original.ksh in CRT window, it disconnects from the server saying not connected Here is my code : (please see the attachment) ____________________________________________________________ #!/bin/ksh ## Load... (1 Reply)
Discussion started by: shruthinagaraj
1 Replies

5. Solaris

Shell Script gives error when run through cron job.

Hi, The following shell script runs without any problem when executed manulally. USED=$(df -h /arch | tail -1 | awk '{print $5}' | cut -d '%' -f 1) if then find /arch/AUBUAT/ -type f -mtime +0 | xargs rm find /arch/AUBMIG/ -type f -mtime +0 | xargs rm fi But the same gives below... (6 Replies)
Discussion started by: ksadiq79
6 Replies

6. Solaris

Cron job running even after cron is removed

Hi , I have removed a cron for particular user , but cron job seems to be running even after the cron entry is removed. The purpose of the cron was to sendmail to user ( it uses mailx utility ) I have restarted cron and sendmail service still user is getting mail alerts from the cron job. And... (4 Replies)
Discussion started by: chidori
4 Replies

7. Shell Programming and Scripting

Cron job fails with [DataDirect][ODBC lib] Connection not open error

Hi, When run the script directly...it executes as expected. But when put it in crontab the job fails with this error: Connection not open 08003: Connection not open Unable to connect to the database... how come it is not able to connect when cron job fires?... Do I need to... (7 Replies)
Discussion started by: nuthakki
7 Replies

8. Shell Programming and Scripting

Commented cron job -- cron monitoring

Hi I have a requirement to write a shell script,that will check the all commented job in cron job.Please help !! (2 Replies)
Discussion started by: netdbaind
2 Replies

9. UNIX for Dummies Questions & Answers

Error while running a script through cron job

Hi Team, When i am running the below query manually it is giving me the right output i.e. export PATH=/usr/sbin:/usr/bin:/sbin:/bin:$PATH ADMIN=abc@abc.com CPU_HIGH=`sar|awk '{print $9}'|sort -n|head -5|sed -n 5p` CPU_MAX=`echo "scale=3; 100-$CPU_HIGH" | bc` CPU_LOW=`sar|awk '{print... (13 Replies)
Discussion started by: Ekamjot
13 Replies

10. Shell Programming and Scripting

Cron job - Need to run Cron every quarter at particular time

Hi, 1) If some job supposed to run on 1st of every month at 7 AM In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day? 2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct) And if 25th... (5 Replies)
Discussion started by: System Admin 77
5 Replies

LEARN ABOUT POSIX

queuedefs

queuedefs(4)                                                       File Formats                                                       queuedefs(4)

NAME

       queuedefs - queue description file for at, batch, and cron

SYNOPSIS

       /etc/cron.d/queuedefs

DESCRIPTION

       The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
       The format of the lines are as follows:

              q.[njobj][nicen][nwaitw]

       The fields in this line are:

       q        The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs  started  by  batch  (see
                at(1)); c is the default queue for jobs run from a crontab(1) file.

       njob     The  maximum  number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
                njob jobs will be run, and the others will be run as jobs that are currently running terminate.  The default value is  100.

       nice     The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user.  The default value is 2.

       nwait    The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in  that  job's
                queue, or because the system-wide limit of jobs executing has been reached.  The default value is 60.

       Lines beginning with # are comments, and are ignored.

EXAMPLES

       Example 1: A sample file.

       #
       #
       a.4j1n
       b.2j2n90w

       This  file  specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
       of 1.  As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before  trying
       again to run it.

       The  b  queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2.  If a job
       cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All  other  queues  can
       have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
       are running cron will wait 60 seconds before trying again to run it.

FILES

       /etc/cron.d/queuedefs           queue description file for  at, batch, and  cron.

SEE ALSO

       at(1), crontab(1), nice(1), cron(1M)

SunOS 5.10                                                          1 Mar 1994                                                        queuedefs(4)
All times are GMT -4. The time now is 11:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy