Bash shell, variables i and rem are working fine in 2 separate for loops, but I'd like to consolidate them like this:
This gives syntax error on &&.
Thanks in advance for direction.
Last edited by p1ne; 07-28-2016 at 02:50 PM..
Reason: no parse
I had different problem scenarios with IF statement. Can any expert please enlighten me on the difference with these scenarios. Thank you.
1st Scenario:
testdate=`date +%Y%m`
test=`cat /var/log/database0.$testdate*.log | grep "Errors found during processing" | tail -10`
if
then
... (4 Replies)
New to scripting in general, so patience plz. If I ask a stupid question or don't get it, I thank you for your kindness in advance.
That said, did a for i loops checks to see if a PB* file is there but I need to know two things before I copy the file.
I need to know if the file's create date... (2 Replies)
Hi,
Actually i stored all validdisks in one array and corresponding partitions required for all individual disks in other array..
Example:
Validdisks=dsk2 dsk3 dsk5
ValidPartition=4 4 3
Now i have to create domain..
Domain creation can be done by below commands:
fs_setup -d... (1 Reply)
I am kind of new in Unix and i have to make a menu. I want to put an if statement in the menu. you should enter the filename and it goes to that file. How do i do this? (1 Reply)
HI Unix Gurus,
I have a number of SELECT count(*) statements in an input file and I want to execute it using a shell script but one by one using loop in script....
How can I do this..... (7 Replies)
1. The problem statement, all variables and given/known data:
Two problems I need solving please. I created a script where the user types in 7 numbers as standard input and each one is then stored in an array. Now I need to perform the following calculations on those numbers:
1) Use a while... (11 Replies)
Hello. I am new here and new to scripting. I used to have a very basic script that worked for simple backup/restore of files. I have expanded it and well... I have ended up with a complete mess. It still backs up and restores but there is so many issues that stem from the many if statements I... (3 Replies)
Say I have a for loop that parse through a file....Say it look for the colors red and blue in sections of the file. Say it find red before it find blue in the file.
Say I have two if statements in the for loop
Something like if blue is found print blue is my favorite color is the first if... (7 Replies)
Discussion started by: scj2012
7 Replies
LEARN ABOUT REDHAT
nanosleep
NANOSLEEP(2) Linux Programmer's Manual NANOSLEEP(2)NAME
nanosleep - pause execution for a specified time
SYNOPSIS
#include <time.h>
int nanosleep(const struct timespec *req, struct timespec *rem);
DESCRIPTION
nanosleep delays the execution of the program for at least the time specified in *req. The function can return earlier if a signal has
been delivered to the process. In this case, it returns -1, sets errno to EINTR, and writes the remaining time into the structure pointed
to by rem unless rem is NULL. The value of *rem can then be used to call nanosleep again and complete the specified pause.
The structure timespec is used to specify intervals of time with nanosecond precision. It is specified in <time.h> and has the form
struct timespec
{
time_t tv_sec; /* seconds */
long tv_nsec; /* nanoseconds */
};
The value of the nanoseconds field must be in the range 0 to 999 999 999.
Compared to sleep(3) and usleep(3), nanosleep has the advantage of not affecting any signals, it is standardized by POSIX, it provides
higher timing resolution, and it allows to continue a sleep that has been interrupted by a signal more easily.
ERRORS
In case of an error or exception, the nanosleep system call returns -1 instead of 0 and sets errno to one of the following values:
EINTR The pause has been interrupted by a non-blocked signal that was delivered to the process. The remaining sleep time has been written
into *rem so that the process can easily call nanosleep again and continue with the pause.
EINVAL The value in the tv_nsec field was not in the range 0 to 999 999 999 or tv_sec was negative.
BUGS
The current implementation of nanosleep is based on the normal kernel timer mechanism, which has a resolution of 1/HZ s (i.e, 10 ms on
Linux/i386 and 1 ms on Linux/Alpha). Therefore, nanosleep pauses always for at least the specified time, however it can take up to 10 ms
longer than specified until the process becomes runnable again. For the same reason, the value returned in case of a delivered signal in
*rem is usually rounded to the next larger multiple of 1/HZ s.
As some applications require much more precise pauses (e.g., in order to control some time-critical hardware), nanosleep is also capable of
short high-precision pauses. If the process is scheduled under a real-time policy like SCHED_FIFO or SCHED_RR, then pauses of up to 2 ms
will be performed as busy waits with microsecond precision.
CONFORMING TO
POSIX.1b (formerly POSIX.4).
SEE ALSO sleep(3), usleep(3), sched_setscheduler(2), timer_create(2)Linux 1.3.85 1996-04-10 NANOSLEEP(2)