01-06-2008
10 More Discussions You Might Find Interesting
1. Programming
Dear Reader,
I'm in a multiprocess environment working with shared mem and semaphores as mutex.. The problem is -- If one of the process hooked up with the semaphore and accessing the shared mem, terminates abruptly ( or got killed ), other process which are in want of the semaphore are... (1 Reply)
Discussion started by: joseph_shibu
1 Replies
2. Programming
Hi there,
Could someone please confirm which POSIX semaphore routines should be used for a multiprocess (and not multithreaded) environment?
sys/sem.h definitely works. but the routines, semget, semctl, semop are pretty unwieldy. So, I am looking for an easier way out.
From the man pages... (2 Replies)
Discussion started by: qntmteleporter
2 Replies
3. Shell Programming and Scripting
Hi Friends,
If i execute this command it comes back with 300 lines:
ipcs|grep cerebrus >>> i would like to clear the semaphores but ipcrm can remove one id at a time. is there a quicker way of removing semaphores maybe using awk?
Regards, (1 Reply)
Discussion started by: kekanap
1 Replies
4. Programming
been searching around on how to use an up and down function with semaphores but i can't find an example. i looked into using: "semop" but i have no idea how to use it. I have been able to declared the semaphores using semget and initializing them using semctl. (7 Replies)
Discussion started by: ddx08
7 Replies
5. UNIX for Advanced & Expert Users
Hello, first of all I apologize if this thread is not in the correct section of this forum, but this one just seemed the most appropriate.
The question I have does not concern Unix specifically, it applies to virtually any OS, however it is in Unix where I learned about this problem.
So, the... (8 Replies)
Discussion started by: Watto86
8 Replies
6. UNIX for Advanced & Expert Users
Hi.
Allocated is showing in hexadecimal which comes to 1 GB
But the usage is showing more (14 GB). Can you please explain why? Normally, usage should be less than allocated
$ /usr/sbin/kmtune -q shmmax
Parameter Current... (4 Replies)
Discussion started by: somesh_p
4 Replies
7. SuSE
Hello all!
On this SLES 10 box I found (what I think) an abnormal huge shmmax value.
hostname:~ # cat /proc/sys/kernel/shmmax
18446744073709551615
hostname:~ #
Perhaps there is a malconfigured startup script on the machine somwhere? But where/how do I find/set the default value of... (2 Replies)
Discussion started by: sap4ever
2 Replies
8. UNIX for Dummies Questions & Answers
I am having problem with semaphores. I am trying to protect line where process prints so that every process with print in proper order.This is the code..
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <sys/ipc.h>
#include <sys/sem.h>
#include <sys/types.h>
union... (3 Replies)
Discussion started by: joker40
3 Replies
9. Programming
Hello Everybody,
I am building a server. this server contains some data. Clients may modify this data or read this data.
If a client is reading the data and at the same time another client is modifying the data then at this case the reading client may read some false data (some old mixed with... (1 Reply)
Discussion started by: Omar_Mokhtar
1 Replies
10. Solaris
Hi,
Can somebody please explain me what semaphores are? there purpose? and there effects?
Thanks in advance:) (0 Replies)
Discussion started by: Laxxi
0 Replies
LEARN ABOUT DEBIAN
email::received
Email::Received(3pm) User Contributed Perl Documentation Email::Received(3pm)
NAME
Email::Received - Parse an email Received: header
SYNOPSIS
use Email::Received;
for ($mail->header("Received")) {
my $data = parse_received($_);
return "SPAM" if rbl_lookup($data->{ip});
}
DESCRIPTION
This module is a Perl Email Project rewrite of SpamAssassin's email header parser. We did this so that the great work they did in analysing
pretty much every possible Received header format could be used in applications other than SpamAssassin itself.
The module provides one function, "parse_received", which takes a single Received line. It then produces either nothing, if the line is
unparsable, a hash reference like this:
{ reason => "gateway noise" }
if the line should be ignored for some good reason, and one like this:
{ ip => '64.12.136.4', id => '875522', by => 'xxx.com',
helo => 'imo-m01.mx.aol.com' }
if it parsed the message. Possible keys are:
ip rdns helo ident envfrom auth by id
RULE FORMAT
Where SpamAssassin used a big static subroutine full of regular expressions to parse the data, we build up a big subroutine full of regular
expressions dynamically from a set of rules. The rules are stored at the bottom of this module. The basic format for a rule looks like
this:
((var=~)?/REGEXP/)? [ACTION; ]+
The "ACTION" is either "SET variable = $value", "IGNORE "reason"?", "UNPARSABLE" or "DONE".
One control structure is provided, which is basically an "if" statement:
GIVEN (NOT)? /REGEXP/ {
ACTION+
}
EXPORT
parse_received
SEE ALSO
Mail::SpamAssassin::Message::Metadata::Received, from which the rules and some of the IP address matching constants were blatantly stolen.
Thanks, guys, for doing such a comprehensive job!
AUTHOR
simon, <simon@>
COPYRIGHT AND LICENSE
Copyright (C) 2006 by simon
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself, either Perl version 5.8.7 or,
at your option, any later version of Perl 5 you may have available.
perl v5.10.0 2006-03-24 Email::Received(3pm)