checking for a flag in a subscript? Post: 302288907

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Calling subscript but sleep halts the main script

Ok, I have written a main script which checks a directory contents every 30 secs then sleeps. The subscript does a usermod, if the user is logged on, it sleeps for 30 secs and then trys again over and over again. Here's the problem. when the subscript is called ./subscript.sh or exec...

2. Shell Programming and Scripting

Shell to run one after another checking any flag or file

a.ksh & b.ksh run at the same time and takes huge resource and time.I want to put a technique so that one wil run after another. eg put a flag so that each script will check if it running , then sleep and wait it to finish. Can some one advise

3. Shell Programming and Scripting

Perl hashes "Can't use subscript on private hash"

This is driving me mad, where am I going wrong? The relevant segment of code: sub getndsybcons { my @servers=@{$_}; my @sybservers=@{$_}; my %results; foreach my $server(@servers) { my $biggestsyb; my $biggestsybval=0; ...

4. AIX

Checking for flag in a subscript?

I want to incorportae a subscript in a job script which is used for loading purposes. What i require is that before a job runs it should check for a flag ,if flag is not present then create it and the loading should start. Once loading finishes it should delete the flag. So if any other load...

5. UNIX for Dummies Questions & Answers

creating a subscript which checks for a flag?

6. Shell Programming and Scripting

How to solve Subscript out of range?

Hi everyone I want to compare numbers line by line Example array = 12 15 15 19 14 I have code: #!bin/csh set a = 1 set b = 2 while($a<6) if($array == $array)then echo "EQUAL" else if($array < $array)then echo "SMALLER" else echo "BIGGER" endif @ a = $a + 1 @ b = $b + 1

7. Shell Programming and Scripting

How to use a subscript and a super script while printing a character

I want to print a output after executing a awk command How to represent a subscript or a superscript while using print command eg : Ts. where character 's' is subscript of T T2 where '2' is the superscript of T thank you. Shashi:

8. UNIX for Dummies Questions & Answers

Name of subscript

I have a script that executes another, so script1 executes script2. Using the $0 variable inside script2 returns the name of script1. How can I get the name of script2? Thanks

9. Shell Programming and Scripting

Checking plsql flag status in UNIX

Hi,I have a stored procedure to verify no of months since current fiscal.I want a shell script to exit with returtn code when the verification fails,I have shell script below but this doesnt work sqlplus / << EOF WHENEVER SQLERROR exit 1 WHENEVER OSERROR exit 2 DECLARE v_time_period...

10. UNIX for Beginners Questions & Answers

Calling subscript with sh vs. ksh

I ran into an issue today that I was able to resolve, but I don't quite understand why the resolution worked. I'm wondering if anyone can help me make sense of it. I have a "kicker" script that calls 4 subscripts on a RHEL 6.9 server. It calls the scripts in sequence checking for a 0 exit code...

LEARN ABOUT BSD

at

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)