|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
Crontab - URGENT pls
Post 6809 by rwb1959 on Wednesday 12th of September 2001 07:24:01 PM
09-12-2001
|
|
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
how to schedule shellscripts using cron tab (2 Replies)
Discussion started by: ss4u
2 Replies
2. Shell Programming and Scripting
Hi,
I am creating a pipe in a directory $HOME/pipes. The pipename should be
L${PROGNAME}. Whenever i embed these lines in shell script, i get an error
mkfifo: No such file or directory.
I am creating a pipe with the key word
mkfifo $HOME/pipes/L${PROGNAME}.
Please help me how to get... (5 Replies)
Discussion started by: raghavan.aero
5 Replies
3. Solaris
Hi everyone,
I would like to know how to compile and run lex programs on solaris 10.
the conventional way is
$ lex <name.l>
$ cc lex.yy.c -ll
$ ./a.out
but while trying to execute the 2nd command :i get a reference saying that the command is old or that main is not supported...
Hence... (1 Reply)
Discussion started by: wrapster
1 Replies
4. Shell Programming and Scripting
Following is d code snipet
#!/bin/ksh
retVal=`sqlplus -s user/passwd\@oracle_sid <<EOF
SET SERVEROUTPUT ON SIZE 100000
DECLARE
STATUS_VALUE VARCHAR2(1);
BEGIN
SELECT temp1 INTO STATUS_VALUE FROM sai;
DBMS_OUTPUT.PUT_LINE(STATUS_VALUE);
END;
/
exit;
EOF`
echo "Return Value... (4 Replies)
Discussion started by: sainathdeg
4 Replies
5. UNIX for Dummies Questions & Answers
Following is d code snipet
#!/bin/ksh
retVal=`sqlplus -s user/passwd\@oracle_sid <<EOF
SET SERVEROUTPUT ON SIZE 100000
DECLARE
STATUS_VALUE VARCHAR2(1);
BEGIN
SELECT temp1 INTO STATUS_VALUE FROM sai;
DBMS_OUTPUT.PUT_LINE(STATUS_VALUE);
END;
/
exit;
EOF`
echo "Return Value... (2 Replies)
Discussion started by: sainathdeg
2 Replies
6. Shell Programming and Scripting
I have downloaded the Putty SSH configuration. I have entered my Host name as illinois.engr.sjsu.edu and i am trying to save that. But i am unable to save.
Also i opened the session and entered my log in name
But it says using keyboard interactive authentication.I am not able to get into $
... (2 Replies)
Discussion started by: VamsiVasili
2 Replies
7. Shell Programming and Scripting
will post again (1 Reply)
Discussion started by: revertback
1 Replies
8. Shell Programming and Scripting
Hi,
These are the text file I have
//input1.txt//
cd dir1/dir2/pg1.txt
cd dir3/dir4/pg2.txt
cd dir88/dir5/pg4.txt
cd dir7/dir6/pg5.txt
cd dir8/dir9/pg7.txt
And each text file has some text.
Now I have to write a shell script which reads input1.txt and changes the directory as shown... (1 Reply)
Discussion started by: bhavanabahety
1 Replies
LEARN ABOUT OPENSOLARIS
queuedefs
queuedefs(4) File Formats queuedefs(4) NAME
queuedefs - queue description file for at, batch, and cron SYNOPSIS
/etc/cron.d/queuedefs DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue. The format of the lines are as follows: q.[njobj][nicen][nwaitw] The fields in this line are: q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see at(1)); c is the default queue for jobs run from a crontab(1) file. njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100. nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2. nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's queue, or because the system-wide limit of jobs executing has been reached. The default value is 60. Lines beginning with # are comments, and are ignored. EXAMPLES
Example 1 A sample file. # # a.4j1n b.2j2n90w This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron. SEE ALSO
at(1), crontab(1), nice(1), cron(1M) SunOS 5.11 1 Mar 1994 queuedefs(4)