02-12-2008
Including ">$outputfile" in your script works fine in case only one output file was originally generated by the Fortran routine. But what should I do when I would like to have two different output files generated in the program? Is it possible to discriminate between different kinds of output, or should I run the program twice (once for each file)?
Anyone with a solution? Thanks in advance.
Last edited by SharkM; 06-05-2008 at 12:22 PM..
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have the following crontab entry to run a shell script for every 30 minutes of every day:
30 * * * * $HOME/main.sh > $HOME/main.log 2>$HOME/error.log
after I created the crontab file I have also done:
$crontab my_crontab
I also check to make sure it exists, by using the following... (11 Replies)
Discussion started by: radhika
11 Replies
2. Shell Programming and Scripting
hi guys,
i have a problem.
a week ago i made a successful crontab that execute bash scripting daily, it worked well
but now, it doesn't work at all, in the mail i have:
"
/home/jimmy/cha/scripts/cekpderr
produced the following output:
lagi jalan
/home/jimmy/cha/scripts/cekpderr:... (6 Replies)
Discussion started by: jimmbp
6 Replies
3. Shell Programming and Scripting
Could someone explain my problem?
I've the following script...
#! /bin/ksh
...
vmquery -m $MediaID | awk '
BEGIN {FS=": "
getline expdate <"ExpDate.txt"
}
$1 ~ /media ID/ {MediaNumber = $NF}
...
$1 ~ /number of mounts/ {
"date +%Y"|getline YearToday
Year4 = YearToday - 4
if... (4 Replies)
Discussion started by: nymus7
4 Replies
4. Shell Programming and Scripting
I have made a script to execute an IDL routine with the purpose to plot data on a fixed time.
The problem is that when I include this script in the crontab to run it every night, the IDL part doesn't work (the other commands, like getting data from the database, are carried out though).
This... (4 Replies)
Discussion started by: SharkM
4 Replies
5. Shell Programming and Scripting
Dear All,
We wrote a script to clean email mailbox when they're nearly full and put it in cron :
0 0 * * * /root/quota/autoclean.sh > /root/quota/autoclean.`date '+%Y%m%d'` 2>&1
I've run this command from command prompt, it did work.
However, if running from cron, it returned such error... (1 Reply)
Discussion started by: tiger2000
1 Replies
6. Shell Programming and Scripting
The .profile file should be read when the user logs in. So, there should be no need to execute .profile file again in a cron job (since the cron job is run after the user logs in). Doesn't the cron require login from the user. Then, from where does the cron execute? Please help!! (1 Reply)
Discussion started by: thulasidharan2k
1 Replies
7. Shell Programming and Scripting
Hi,
I am trying to execute a script (for once) during the booting time in Ubuntu system. However, the result is only showing the strings without without the variables.
Here is the script:
MgrIp=$(ec2-describe-instances --filter tag:Name=Mgr --filter instance-state-name=running | egrep... (4 Replies)
Discussion started by: turki_00
4 Replies
8. Shell Programming and Scripting
Hi Expert,
I have a .sh script in my home/new_dir/script.sh
This script creates number of output files at home/new_dir/email, home/new_dir/logs dir.
I am running this script using crontab (owner root).
Now this output files are getting created with
rw-r----- 1 root root
So if i... (2 Replies)
Discussion started by: Jeet1982
2 Replies
9. Shell Programming and Scripting
Hello
I have a problem with the crontab command
when I run a code containing Curl on the command line it runs without fail but as soon as I program it with crontab it executes everything except the curl returns fail
thank you for helping me to resolve this problem because since Monday I look... (14 Replies)
Discussion started by: beautymind
14 Replies
10. Shell Programming and Scripting
I have set several cron jobs. I recently added a new cron job that copies a file of last day from another server and is executed each day (for example at 04:00 am) but when I check next day the file hasn't been copied.
I'm working in GNU/Linux CentOS (2.6.32) system.
The files that I need to... (23 Replies)
Discussion started by: Ophiuchus
23 Replies
LEARN ABOUT REDHAT
crontab
CRONTAB(1) General Commands Manual CRONTAB(1)
NAME
crontab - maintain crontab files for individual users (V3)
SYNOPSIS
crontab [ -u user ] file
crontab [ -u user ] { -l | -r | -e }
DESCRIPTION
Crontab is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user can have
their own crontab, and though these are files in /var, they are not intended to be edited directly.
If the allow file exists, then you must be listed therein in order to be allowed to use this command. If the allow file does not exist but
the deny file does exist, then you must not be listed in the deny file in order to use this command. If neither of these files exists,
then depending on site-dependent configuration parameters, only the super user will be allowed to use this command, or all users will be
able to use this command.
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(8) can confuse crontab and that if you are running
inside of su(8) 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.
SEE ALSO
crontab(5), cron(8)
FILES
/etc/cron.allow
/etc/cron.deny
STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as
well as from the classic SVR3 syntax.
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
AUTHOR
Paul Vixie <paul@vix.com>
4th Berkeley Distribution 29 December 1993 CRONTAB(1)