03-25-2013
Re-directing issue.
Hi All,
Have scheduled a cron entry to run once a week.
0 0 * * 1 /export/home/nz/history_load/prod/LoadManager.sh >>/dev/null 2>&1
Not sure, why this job did not got triggered last week. Want to know the reason behind not getting triggered.
I was re-directing the output of the command to >>/dev/null 2>&1
instead of logfile. Please let me know is there a way to chek this?
Thanks and Regards
Nagaraja Akkivalli.
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I'm trying to locate all files that do not contain the string /usr but do contain the string csh within the file called /etc/passwd. Then I would like to direct this output to a file called pout.
Does anyone one have suggestions on this one?
Thanks (2 Replies)
Discussion started by: klannon
2 Replies
2. UNIX for Dummies Questions & Answers
How do I direct the output of an at command
at now < backupprogram
so that I see something happening. It says the job has been executed but I am not getting the tar file that my backup program on the computer anywhere at all
Please help me - I really am a struggling begginer. (1 Reply)
Discussion started by: Cynergetix
1 Replies
3. UNIX for Advanced & Expert Users
Hi,
I'm running a program by executing the following command...
convert NA 2> compiler.err
Here is the command for debugging this process in IBM debugger...
idebug convert NA 2> compiler.err
On executing the above command the error output from idebug process is
redirected to compiler.err,... (3 Replies)
Discussion started by: fermisoft
3 Replies
4. Programming
Hi,
I just wrote a program in C to split a comma seperated string in to group of strings using strtok() function. The code is:
int main()
{
char *temp;//not used here but basically we extract one string after another using strtok() and assign to a string pointer defined like this.
... (3 Replies)
Discussion started by: SankarV
3 Replies
5. Shell Programming and Scripting
When I do
time tar cvf /dev/st0 /mnt/junk >> /root/benchlog, I want it to put the output of the time command into the benchlog file, but it put /mnt/junk. How do I get it to put the output of the tar command? (1 Reply)
Discussion started by: jeriryan87
1 Replies
6. Shell Programming and Scripting
I have a script in which some outputs are directed to one file
echo "Load Started" >>${LOGFILE1}
If I have another file LOGFILE2 and i want to redirect the output of the above echo command to LOGFILE2 as well with the same command line... how can i do that?
Thanks (2 Replies)
Discussion started by: cobroraj
2 Replies
7. Shell Programming and Scripting
Dear All
I have a simple bash script that creates a folder ( I called it TEMP) in the current directory.
The question is: how do I direct the output of my awk script into folder TEMP?
Below is my attempt:
#!/bin/bash
mkdir TEMP
echo Enter input file:
read infile
awk... (4 Replies)
Discussion started by: Ghetz
4 Replies
8. Shell Programming and Scripting
Is there a way to keep the output of a script displayed on the terminal when it's run by itself, but suspend part of that output and only have a specific part delivered when it's piped to another script or program? I'm thinking something like the following pseudocode:
#!/bin/bash
... (1 Reply)
Discussion started by: trigg
1 Replies
9. UNIX Desktop Questions & Answers
ps –xyz >/tmp/proc 2>&1
Can anyone explain what does '2' and '&1' will do here?
Thanks to explain (1 Reply)
Discussion started by: kkalyan
1 Replies
10. Shell Programming and Scripting
Hi,
I still have the problem with directing information from cat or grep to a variable.
For instance:
XMSG "$(date +%Y_%m_%d)_error_report.txt" "$(cat "$(date +%Y_%m_%d)_error_report.txt")" &Works! The text received by cat is directed to my function.
If it is written like this, my... (2 Replies)
Discussion started by: haukee
2 Replies
AT(1) General Commands Manual AT(1)
NAME
at - execute commands at a later time
SYNOPSIS
at [ -c ] [ -s ] [ -m ] time [ day ] [ file ]
DESCRIPTION
At spools away a copy of the named file to be used as input to sh(1) or csh(1). If the -c flag (for (csh(1))) or the -s flag (for (sh(1)))
is specified, then that shell will be used to execute the job; if no shell is specified, the current environment shell is used. If no file
name is specified, at prompts for commands from standard input until a ^D is typed.
If the -m flag is specified, mail will be sent to the user after the job has been run. If errors occur during execution of the job, then a
copy of the error diagnostics will be sent to the user. If no errors occur, then a short message is sent informing the user that no errors
occurred.
The format of the spool file is as follows: A four line header that includes the owner of the job, the name of the job, the shell used to
run the job, and whether mail will be set after the job is executed. The header is followed by a cd command to the current directory and a
umask command to set the modes on any files created by the job. Then at copies all relevant environment variables to the spool file. When
the script is run, it uses the user and group ID of the creator of the spool file.
The time is 1 to 4 digits, with an optional following `A', `P', `N' or `M' for AM, PM, noon or midnight. One and two digit numbers are
taken to be hours, three and four digits to be hours and minutes. If no letters follow the digits, a 24 hour clock time is understood.
The optional day is either (1) a month name followed by a day number, or (2) a day of the week; if the word `week' follows, invocation is
moved seven days further off. Names of months and days may be recognizably truncated. Examples of legitimate commands are
at 8am jan 24
at -c -m 1530 fr week
at -s -m 1200n week
At programs are executed by periodic execution of the command /usr/libexec/atrun from cron(8). The granularity of at depends upon the how
often atrun is executed.
Error output is lost unless redirected or the -m flag is requested, in which case a copy of the errors is sent to the user via mail(1).
FILES
/usr/spool/at spooling area
/usr/spool/at/yy.ddd.hhhh.* job file
/usr/spool/at/past directory where jobs are executed from
/usr/spool/at/lasttimedone last time atrun was run
/usr/libexec/atrun executor (run by cron(8))
SEE ALSO
atq(1), atrm(1), calendar(1), sleep(1), cron(8)
DIAGNOSTICS
Complains about various syntax errors and times out of range.
BUGS
Due to the granularity of the execution of /usr/libexec/atrun, there may be bugs in scheduling things almost exactly 24 hours into the
future.
If the system crashes, mail is not sent to the user informing them that the job was not completed.
Sometimes old spool files are not removed from the directory /usr/spool/at/past. This is usually due to a system crash, and requires that
they be removed by hand.
4th Berkeley Distribution October 21, 1996 AT(1)