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 PHP
posix_madvise
POSIX_MADVISE(3) Linux Programmer's Manual POSIX_MADVISE(3)
NAME
posix_madvise - give advice about patterns of memory usage
SYNOPSIS
#include <sys/mman.h>
int posix_madvise(void *addr, size_t len, int advice);
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
posix_madvise():
_POSIX_C_SOURCE >= 200112L
DESCRIPTION
The posix_madvise() function allows an application to advise the system about its expected patterns of usage of memory in the address range
starting at addr and continuing for len bytes. The system is free to use this advice in order to improve the performance of memory
accesses (or to ignore the advice altogether), but calling posix_madvise() shall not affect the semantics of access to memory in the speci-
fied range.
The advice argument is one of the following:
POSIX_MADV_NORMAL
The application has no special advice regarding its memory usage patterns for the specified address range. This is the default
behavior.
POSIX_MADV_SEQUENTIAL
The application expects to access the specified address range sequentially, running from lower addresses to higher addresses.
Hence, pages in this region can be aggressively read ahead, and may be freed soon after they are accessed.
POSIX_MADV_RANDOM
The application expects to access the specified address range randomly. Thus, read ahead may be less useful than normally.
POSIX_MADV_WILLNEED
The application expects to access the specified address range in the near future. Thus, read ahead may be beneficial.
POSIX_MADV_DONTNEED
The application expects that it will not access the specified address range in the near future.
RETURN VALUE
On success, posix_madvise() returns 0. On failure, it returns a positive error number.
ERRORS
EINVAL addr is not a multiple of the system page size or len is negative.
EINVAL advice is invalid.
ENOMEM Addresses in the specified range are partially or completely outside the caller's address space.
VERSIONS
Support for posix_madvise() first appeared in glibc version 2.2.
CONFORMING TO
POSIX.1-2001.
NOTES
POSIX.1 permits an implementation to generate an error if len is 0. On Linux, specifying len as 0 is permitted (as a successful no-op).
In glibc, this function is implemented using madvise(2). However, since glibc 2.6, POSIX_MADV_DONTNEED is treated as a no-op, because the
corresponding madvise(2) value, MADV_DONTNEED, has destructive semantics.
SEE ALSO
madvise(2), posix_fadvise(2)
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
Linux 2017-09-15 POSIX_MADVISE(3)