01-20-2006
Thank you - you nailed it
I escaped the % sign and it now works fine
crontab -l >/FIXENGINE/data/crontab.$(whoami).$(date +\%a)
Thank you again
John
BTW - am running HPUX 11
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
I'm stuck and confused as to why when I execute things form the command line it works but when in a script it doesn't.
My script:
### creating a lock on the console
touch /var/run/console.lock
chmod 600 /var/run/console.lock
echo "$User" >>... (2 Replies)
Discussion started by: larry
2 Replies
2. UNIX for Dummies Questions & Answers
Hello,
I have put the following command in a shell script:
ncopy /home/Selma/my_file server2\!INPUT/my_file userpassword
(server2 is the remote machine)
The script works fine when it is invoked manually, however when it is scheduled to be run from crontab ncopy doesn't work (all of the... (2 Replies)
Discussion started by: Selma
2 Replies
3. Shell Programming and Scripting
The script checks for free space stats on Oracle. If there are any tablespaces with more than 85% usage it prints the details of the tablespace. If all the tablespaces have more than 15% free space, then "All tablespaces have more than 15 pct free space" must be printed on the screen.
When I run... (2 Replies)
Discussion started by: RoshniMehta
2 Replies
4. Shell Programming and Scripting
Hi....
cd command is not working when dual string drive/volume name is passed to cd through variables.......
For Ex....
y=/Volumes/Backup\ vipin/
cd $y
the above command gives error.......
anyone with a genuine solution ? (16 Replies)
Discussion started by: vipinchauhan222
16 Replies
5. UNIX for Dummies Questions & Answers
Hello all,
Something strange going on with a shell script I'm writing. It's trying to write a list of files that it finds in a given directory to another file. But I also have a skip list so matching files that are in that skip list should be, well uhm, skipped :)
Here's the code of my... (2 Replies)
Discussion started by: StijnV
2 Replies
6. Shell Programming and Scripting
Hi, I have a question.
I define a function using sed command:
replace()
{
searchterm=$1
replaceterm=$2
sed -e "s/$searchterm/$replaceterm/ig" $3 > $WORK'tempfile.tmp'
mv $WORK'tempfile.tmp' $3
}
Then I call
replace 'test = 0' 'test = 1' $myfileThis code works well in... (1 Reply)
Discussion started by: Dark2Bright
1 Replies
7. Shell Programming and Scripting
Hi, I have a question.
I define a function using sed command:
replace()
{
searchterm=$1
replaceterm=$2
sed -e "s/$searchterm/$replaceterm/ig" $3 > $WORK'tempfile.tmp'
mv $WORK'tempfile.tmp' $3
}
Then I call
replace 'test = 0' 'test = 1' $myfile
This code... (1 Reply)
Discussion started by: Dark2Bright
1 Replies
8. Solaris
Hi All,
I am using a solaris Sun-Fire-V440 server.
The OS is solaris.
My problem is whenever I run the command
mount | grep "^/ " | sed -e 's,^.*dsk/\(*\).*$,\1,'
it should return a disk value as "d30" as it does on each of my other servers.But on this server I am not getting any o/p from... (3 Replies)
Discussion started by: vivek.goel.piet
3 Replies
9. Shell Programming and Scripting
I have 10 application servers in a distributed architecture generating their own application logs. Each server has application utility to continuously tail the log. for example following command follows tails and follows new logfiles as they are generated
server1$ logutility logtype
When I run... (8 Replies)
Discussion started by: indianya
8 Replies
10. UNIX for Dummies Questions & Answers
My unzip command doesn't work for files that are greater than 4GB. Consider my file name is unzip -p -a filename.zip, the command doesn't work since the size of the file is larger. I need to know the corresponding 7z command for the same. This is my Unix shell script program:
if
then
... (14 Replies)
Discussion started by: chandraprakash
14 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