Sponsored Content
Full Discussion: email Alert
Top Forums Shell Programming and Scripting email Alert Post 302139505 by fed.linuxgossip on Sunday 7th of October 2007 07:51:21 PM
Old 10-07-2007
IDS is fine too.. but I want an advice on that script too.
 

4 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Email alert script

I need to code a script, which will run via cron, every 30 minutes. The script will read a file containing a date&time and number (which represents disk space). The file gets appended to every 30 minutes. Here's a sample of the file: CPU 1:04/25/02 1:00 am:1972554 CPU 1:04/25/02 1:30... (1 Reply)
Discussion started by: moon
1 Replies

2. Shell Programming and Scripting

Using top command to email if process is exceeding 25% and sending an email alert if so

This is my first time writing a script and Im having some trouble, Im trying to use the top command to monitor processes and the amount of CPU usage they require, my aim is to get an email if a process takes over a certain percentage of CPU usage I tried grep Obviosly that hasnt worked, Any... (8 Replies)
Discussion started by: jay02
8 Replies

3. UNIX for Beginners Questions & Answers

Email Alert in UNIX

Hi There I have to wrote a script where I am able to echo a result of an SQL script, however I want to be able to send an email to myself when it is more than 0 (so whenever a value is returned) is this possible? I tried one way from looking on the web but this didn't work, I have added my... (8 Replies)
Discussion started by: simpsa27
8 Replies

4. Shell Programming and Scripting

Email alert after termination

I am running the gaussian program on UNIX with bash and I want to form a script that will email me once the output life terminates either "normal termination" or "false" I just started learning this last week so could you let me know how to go about this.:b: (13 Replies)
Discussion started by: Jade_Michael
13 Replies
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
All times are GMT -4. The time now is 05:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy