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
2) using cron
Please let me know what can be the problem here
Thanks in advance
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)
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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT NETBSD
crontab
CRONTAB(1) BSD General Commands Manual CRONTAB(1)NAME
crontab -- maintain crontab files for individual users (ISC Cron V4.1)
SYNOPSIS
crontab [-u user]
crontab [-elr]
DESCRIPTION
crontab is the program used to install, deinstall, or list the tables used to drive the cron(8) daemon in ISC Cron. Each user can have their
own crontab, and though these are files in /var/cron, they are not intended to be edited directly.
If the /var/cron/allow file exists, then you must be listed therein in order to be allowed to use this command. If the /var/cron/allow file
does not exist but the /var/cron/deny file does exist, then you must not be listed in the /var/cron/deny file in order to use this command.
If neither of these files exists, depending on the compiled in settings, only the super user will be allowed to use this command, or everyone
will be allowed to use this command. On NetBSD everyone is allowed to use this command.
The default maximum size for a crontab is 256 kilobytes, but this may be changed for all users on the system by putting the desired maximum
size (in bytes) in the /var/cron/maxtabsize file.
If the -u option is given, it specifies the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines
``your'' crontab, i.e., the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running
inside of su(1) you should always use the -u option for safety's sake.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename ``-'' is given.
The -l option causes the current crontab to be displayed on standard output.
The -r option causes the current crontab to be removed.
The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit
from the editor, the modified crontab will be installed automatically.
FILES
/var/cron/allow Optional list of users that are allowed to use crontab.
/var/cron/deny Optional list of users that are disallowed to use crontab.
/var/cron/maxtabsize Maximum size of crontab files. Defaults to 256 kilobytes.
/var/cron/tabs/ Directory containing the individual user crontab files, named after the user.
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO crontab(5), cron(8)STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). This new command syntax differs from previous versions of Vixie Cron, as well
as from the classic Version 3 AT&T UNIX syntax.
AUTHORS
Paul Vixie <vixie@isc.org>
BSD May 6, 2010 BSD