[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: programming questions. topics process , signals , IPC
On Tue, 11 May 1999 Nezer.Zaidenberg@ecitele.com wrote:
> how can I convince child process not to send SIGCHLD to the father (and thus not
> remain zombie)?
if i remember correctly, you could simply set the signal handler of SIGCHL
to SIGIGN (ignore), and then child processes are 'ripped off'
automatically by the system (at least according to w. richard stevens).
> how can I change the max size of Message Queue (Sys V IPC message queue)
as far as i know, in linux, this is a kernel compile-time option. it
appears to be defined in /usr/include/linux/msg.h , the constant name is
'MSGMNB'. I'd assume that modifying this parameter and then recompiling
the kernel would change this value...
on the other hand, according to the kernel's code
(/usr/src/linux/ipc/msg.c), it appers that root may use a msgctl call
with the IPC_SET flag may be used to modify this limitat runtime.
> also, when trying to run my prgoram on old SunOS machine the machine
> refused to send message to the message queue saying "no more processes"
> does SVR4 machines open a new process when trying to open msg queue? is
> there a way to avoid it? does SunOS open a new process?
i'm not aware of any operating system spawning a new process in order to
send a message on a message queue. youmust have had some other problem.
which process/command/system call exactly gave you this message? could it
be that you took this improperly from errno (i.e. miss-read errno and thus
when translating to a string, got the wrong error message)?
guy