Sponsored Content
Full Discussion: Command syntax error in cron
Top Forums UNIX for Advanced & Expert Users Command syntax error in cron Post 303015417 by migurus on Wednesday 4th of April 2018 02:59:40 PM
Old 04-04-2018
Command syntax error in cron

SCO OSR 507, user's shell is old Bourne sh
The same command is OK when run using now, but fails when run in cron, see below:

1) using now, see how it worked and I see resulting DT=2018 in the mail
Code:
 
 $ at now
{ dt=`/usr/gnu/bin/date '+%Y'`; echo "DT=$dt"; }
job 1522867418.a-6605:0 at Wed Apr  4 11:43:38 2018
$ mail
SCO OpenServer Mail Release 5.0.7  Type ? for help.
"/usr/spool/mail/test": 1 message 1 new
>N  1 cron@test.testdo Wed Apr  4 19:43   19/639   Output of one of your cron 
& 
Message  1:
From cron Wed Apr  4 18:43:43 2018
Return-Path: <cron>
... snipped for brevity ...
Subject: Output of one of your cron jobs
Date: Wed, 4 Apr 2018 11:43:42 -0700 (PDT)
Status: R
 DT=2018

2) using cron
Code:
 
 $ crontab -l
 44 11 * * * { dt=`/usr/gnu/bin/date '+%Y'`; echo "DT=$dt"; }
 $ mail
 $ mail
SCO OpenServer Mail Release 5.0.7  Type ? for help.
"/usr/spool/mail/test": 1 message 1 new
>N  1 cron@test.testdo Wed Apr  4 19:44   19/696   Output of one of your cron 
& 
Message  1:
From cron Wed Apr  4 18:44:01 2018
Return-Path: <cron>
Received: (from cron@localhost)
...
Subject: Output of one of your cron jobs
Date: Wed, 4 Apr 2018 11:44:00 -0700 (PDT)
Status: R
 /bin/sh: syntax error at line 1: `end of file' unexpected
 
*************************************************
Cron: The previous message is the standard output and standard error
     of the following cron job, executed on your behalf:
{ dt=`/usr/gnu/bin/date '+
&

Please let me know what can be the problem here
Thanks in advance
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

until command syntax error

Hi there. I spent too much time away from Unix, now I can't remember how to issue a simple until command in ksh :mad: could you tell me what is wrong with the following code sample: export v = "1" until do echo 'executing repeat_until' v = `expr $v + 1` done I've... (3 Replies)
Discussion started by: 435 Gavea
3 Replies

2. Shell Programming and Scripting

if else command syntax error

can anyone tell me what`s going wrong with my if else statement? set exam=(AAA BBB CCC) foreach ii ($exam) if ($ii -eq "AAA") do echo "PASS" else echo "FAILED" done end (4 Replies)
Discussion started by: c0384
4 Replies

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

4. Solaris

please review this cron syntax

Dears if i want to run this job every Saturday at 6 AM that will be the code * 6 * * 1 cd /export/home/jenova ; ls -ltr >> $HOME/jenova_dir (2 Replies)
Discussion started by: jenovaux
2 Replies

5. Shell Programming and Scripting

bash syntax error: command not found

I am trying to create a shell that asks the user to enter their name, and compare it to my own by saying we have the same name or saying my name and that they have a nice name too. Here is my script... #!/bin/bash-x echo "Enter your name". read name if then echo "My name is Adam too"... (1 Reply)
Discussion started by: amaxey45
1 Replies

6. Shell Programming and Scripting

Syntax error using do command

i have the following do command: while IFS =: read printer drv IP port do echo -e "$ printer: \ n \ drv: \ t $ drv \ n \ IP: \ t $ IP \ n \ port: \ t $ port \ n \" done < diffs.txt receiving the following error: syntax error at line 37 : `do' unmatched something is... (2 Replies)
Discussion started by: ggoliath
2 Replies

7. Shell Programming and Scripting

Syntax error piping to bc on command line - works when assigned to var

I have a script which outputs some timing data a line at a time. There are approx. 10 lines echoed, each line looks something like this: 0.741 http://checkip.dyndns.org 94.170.119.226Since I needed to add all the values in the first column, I piped the output to grep, matching and printing the... (7 Replies)
Discussion started by: gencon
7 Replies

8. Shell Programming and Scripting

Getting syntax error while running awk command

Hello Gurus, I am firing the below command : df -g | grep -v var| awk '{ (if $4 > 90% ) print "Filesystem", $NF,"over sized";}' But I am getting the below error:- ====== syntax error The source line is 1. The error context is {if ($4 > >>> 90%) <<< awk: The... (9 Replies)
Discussion started by: pokhraj_d
9 Replies

9. Shell Programming and Scripting

Syntax error with ps command

i am trying the blow command in vain on Linux Terminal. kill -9 `ps -eaf | grep weblogic.NodeManager | grep wls103 | awk '{print $2}'` kill: usage: kill pid | jobspec ... or kill -l kill -9 $(ps -eaf | grep weblogic.NodeManager | grep wls103| awk '{print $2}') kill: usage: kill pid |... (7 Replies)
Discussion started by: mohtashims
7 Replies

10. Shell Programming and Scripting

(standard_in)1:syntax error using bc with Cron

I created a shell script to record server temperature. When I manually run script it works fine with no error message. But when I create a cron job, my script fails with error message (standard_in)1:syntax error. I figured out the bc utility is causing the error message. Below is my script. ... (7 Replies)
Discussion started by: SysAdminRialto
7 Replies
cron(8) 						      System Manager's Manual							   cron(8)

NAME
cron - The system clock daemon SYNOPSIS
/usr/sbin/cron DESCRIPTION
The cron daemon runs shell commands at specified dates and times. Commands that are to run according to a regular or periodic schedule are found within the crontab files. Commands that are to run once only are found within the at files. You submit crontab and at file entries by using the crontab and at commands. Because the cron process exits only when killed or when the system stops, only one cron daemon should exist on the system at any given time. Normally, you start the cron daemon from within a run command file. During process initialization and when cron detects a change, it examines the crontab and at files. This strategy reduces the overhead of checking for new or changed files at regularly scheduled intervals. The cron command creates a log of its activities. The cron daemon must be started from the system startup scripts because it must begin execution without a login user ID set. The cron daemon starts each job with the following process attributes stored with the job by the invoking process: Login user ID Effective and real user IDs Effective and real group IDs Supplementary groups It also establishes the following attributes from the authentication profile of the account associated with the login user ID of the invok- ing process: Audit control and disposition masks Kernel authorizations DIAGNOSTICS
The at and batch programs will refuse to accept jobs submitted from processes whose login user ID is different from the real user ID. FILES
Specifies the command path. Main cron directory Directory containing the crontab files. List of allowed users. List of denied users His- tory information for cron Queue description file for at, batch, and cron RELATED INFORMATION
Commands: at(1), crontab(1), rc0(8), rc2(8), rc3(8) Files: queuedefs(4) delim off cron(8)
All times are GMT -4. The time now is 09:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy