Thank you for your reply. I think I have found quicker and safer solution for problem.
I've removed all my code from signal handler and added variable increment.
This isn't threadsafe. Variables aren't atomic and/or threadsafe on their own, that's why we need things like mutexes and semaphores.
All your solution amounts to is exactly what I suggested anyway: doing sem_post in the interrupt handler(increment the semaphore), and sem_wait inside the thread(decrement the semaphore). Treat the semaphore like a thread-safe integer that blocks the thing trying to decrement it if it goes below zero. You don't have to post and wait in both, it's not a mutex.
Quote:
I'm using SA_RESTART flag so if sem_wait() or sem_post() are interrupted by signal, they will be restarted. Now I have semaphores inside infinite loop inside main program and in threads. I don't think I should experience similar problem again.
What do you think?
You didn't expect them to fail before, either. You can't account for everything. Always check the return value of an important system call, it's not optional!
Last edited by Corona688; 09-03-2010 at 02:12 PM..
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)
Hi all,
I am using HP 10.20 on A 9000/785. My question is:
If I am the only person logged in as root at the moment, how many "semaphore proccesses" should I have?? Is it only one, or it is relevant to other system proccesses?
Here is what I get listing the current semaphores
# ipcs -sp... (1 Reply)
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)
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)
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)
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)
Hello,
I was doing an exercise of semaphores and shared memory, namely the barbers:
-B number of barbers
-S number of chairs
-C number of customers.
I have done already and I compiled the code, but when run I get an error segment. Can not be and it took several days.
If anyone sees the error... (2 Replies)
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)
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)
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 NETBSD
wakeonlan
WAKEONLAN(8) BSD System Manager's Manual WAKEONLAN(8)NAME
wakeonlan -- send Wake on LAN frames to hosts on a local Ethernet network
SYNOPSIS
wakeonlan [interface] lladdr [lladdr ...]
DESCRIPTION
The wakeonlan program is used to send Wake on LAN (WoL) frames over a local Ethernet network to one or more hosts using their link layer
(hardware) addresses. WoL functionality is generally enabled in a machine's BIOS and can be used to power on machines from a remote system
without having physical access to them.
interface is an Ethernet interface of the local machine and is used to send the Wake on LAN frames over it. If there is only one Ethernet
device available that is up and running, then the interface argument can be omitted. lladdr is the link layer address of the remote machine.
This can be specified as the actual hardware address (six hexadecimal numbers separated by colons) or as a hostname entry in /etc/ethers.
wakeonlan accepts multiple lladdr addresses. Link layer addresses can be determined and set using ifconfig(8).
FILES
/etc/ethers Ethernet host name data base.
SEE ALSO ethers(5), ifconfig(8)AUTHORS
wakeonlan was written by Marc Balmer <marc@msys.ch>.
BSD May 25, 2012 BSD