10-14-2013
Thanks a lot for that. I have a few other thing I'd like to do to improve my scripts, is here the best place to ask for advice?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
#!/usr/bin/bash
###script to input four characters. wxyz
echo "input first string"
read instring1
echo "input second string"
read instring2
##
echo "first string is:" $instring1
echo "second string is:" $instring2
##IF instring1 or instring2 are NOT 4 characters (xxxx) , exit 1.
##how??
... (2 Replies)
Discussion started by: ajp7701
2 Replies
2. Shell Programming and Scripting
Hello friends,
Kindly help me in developing a script that asks user to enter a value and will wait for 5 seconds for the feedback. If there is no answer from the user the script will perform exit or it will continue doing something else
Ex: If yu have a multi OS system i believe while... (3 Replies)
Discussion started by: frozensmilz
3 Replies
3. Shell Programming and Scripting
Folks,
Below is a basic synopsis of the problem. I have a script that I need to check for some env vars and fail (exit the script) if they are not there. At the same time I need to set some default env vars. To do this I must run the script from the parent shell or source the script. Doing... (3 Replies)
Discussion started by: bashN00b
3 Replies
4. Shell Programming and Scripting
Solved Stupidly I didn't put brackets around the , thanks for all the help guys
if ps ax | grep Cluster__check.bash | grep -v grep > /dev/null -- fails
(if ps ax | grep Cluster__check.bash | grep -v grep > /dev/null) --works (3 Replies)
Discussion started by: danmc
3 Replies
5. Shell Programming and Scripting
Here is my daily stupid question:
How can I tell a script to only execute if the other scripts exits successfully?
So "script A" executes and it executes successfully (0),then "script B" will run
or else
"script A "executes and it exits unsucessfully (1) then "script B" will read return... (6 Replies)
Discussion started by: metallica1973
6 Replies
6. Shell Programming and Scripting
Hi, I want to write a script to check whether an user ID is used in my server and then create that user.
If the user ID is not used, I will echo something like "OK, continue" and then continue to execute the script. Else, I will echo something like "Used, exit" and then exit the script.
As... (4 Replies)
Discussion started by: dirkaulo
4 Replies
7. Shell Programming and Scripting
Hi, I have written a script that allows me to repetitively play a music file $N times, which is specified through user input. However, if I want to exit the script before it has finished looping $N times, if I use CTRL+c, I have to CTRL+c however many times are left in order to complete the loop.... (9 Replies)
Discussion started by: hilltop_yodeler
9 Replies
8. Shell Programming and Scripting
Heyas,
Since this question (similar) occur every now and then, and given the fact i was thinking about it just recently (1-2 weeks) anyway, i started to write something :p
The last point for motivation was... (17 Replies)
Discussion started by: sea
17 Replies
9. Shell Programming and Scripting
Hello all..
so i have a problem i need to solve ..
#! /bin/bash
$SHELL
dtterm -title my_prog -e su -user -c 'export DISPLAY=:0.0 ; /path/to/my/prog' & 2> /dev/null
$SHELL
intr
exit
This script will work on solaris 10 system in right clikt menu - in a secure system so i need to... (0 Replies)
Discussion started by: defs
0 Replies
10. Shell Programming and Scripting
Hi everyone, I'm new here and just a beginner in linux scripting.
Just want to ask for help on this one.
I am trying to create a script that will accept user input (year-month and user/s).
I wanted to have the script to continue running, until the user inputs a DATE and name/s of user/s. ... (2 Replies)
Discussion started by: Helskadi
2 Replies
LEARN ABOUT OSX
posix_madvise
MADVISE(2) BSD System Calls Manual MADVISE(2)
NAME
madvise, posix_madvise -- give advice about use of memory
SYNOPSIS
#include <sys/mman.h>
int
madvise(void *addr, size_t len, int advice);
int
posix_madvise(void *addr, size_t len, int advice);
DESCRIPTION
The madvise() system call allows a process that has knowledge of its memory behavior to describe it to the system. The advice passed in may
be used by the system to alter its virtual memory paging strategy. This advice may improve application and system performance. The behavior
specified in advice can only be one of the following values:
MADV_NORMAL Indicates that the application has no advice to give on its behavior in the specified address range. This is the system
default behavior. This is used with madvise() system call.
POSIX_MADV_NORMAL
Same as MADV_NORMAL but used with posix_madvise() system call.
MADV_SEQUENTIAL Indicates that the application expects to access this address range in a sequential manner. This is used with madvise()
system call.
POSIX_MADV_SEQUENTIAL
Same as MADV_SEQUENTIAL but used with posix_madvise() system call.
MADV_RANDOM Indicates that the application expects to access this address range in a random manner. This is used with madvise() system
call.
POSIX_MADV_RANDOM
Same as MADV_RANDOM but used with posix_madvise() system call.
MADV_WILLNEED Indicates that the application expects to access this address range soon. This is used with madvise() system call.
POSIX_MADV_WILLNEED
Same as MADV_WILLNEED but used with posix_madvise() system call.
MADV_DONTNEED Indicates that the application is not expecting to access this address range soon. This is used with madvise() system call.
POSIX_MADV_DONTNEED
Same as MADV_DONTNEED but used with posix_madvise() system call.
MADV_FREE Indicates that the application will not need the information contained in this address range, so the pages may be reused
right away. The address range will remain valid. This is used with madvise() system call.
MADV_ZERO_WIRED_PAGES
Indicates that the application would like the wired pages in this address range to be zeroed out if the address range is
deallocated without first unwiring the pages (i.e. a munmap(2) without a preceding munlock(2) or the application quits).
This is used with madvise() system call.
The posix_madvise() behaves same as madvise() except that it uses values with POSIX_ prefix for the advice system call argument.
RETURN VALUES
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error.
ERRORS
madvise() fails if one or more of the following are true:
[EINVAL] The value of advice is incorrect.
[EINVAL] The address range includes unallocated regions.
[ENOMEM] The virtual address range specified by the addr and len are outside the range allowed for the address space.
LEGACY SYNOPSIS
#include <sys/types.h>
#include <sys/mman.h>
int
madvise(caddr_t addr, size_t len, int advice);
int
posix_madvise(caddr_t addr, size_t len, int advice);
The include file <sys/types.h> is necessary. The type of addr has changed.
SEE ALSO
mincore(2), minherit(2), mprotect(2), msync(2), munmap(2), compat(5)
HISTORY
The madvise function first appeared in 4.4BSD. The posix_madvise function is part of IEEE 1003.1-2001 and was first implemented in Mac OS X
10.2.
BSD
June 9, 1993 BSD