Good Afternoon,
The following post "how-get-program-name-produced-io-error-redirected-log-nohup-command" is already answered. You can go ahead and close it. Thanks for your help.
Best regards. (1 Reply)
i must close server after a specific user input, such as FINE, if i put a test inside function "maiuscolatore" i receive an error on second recv of client. why?
below there are code of client and server:
CLIENT:
#include <stdlib.h>
#include <stdio.h>
#include... (0 Replies)
Hello everyone
I have a user on my server, Aix 5.3 TL9 sp4. Weeks ago I dont have a problem but today the user cannot log in. let me explain.
Me with root user I can change his password. then I log in with the user and I can change the password and the terminal close. Im using ssh.
But... (2 Replies)
Discussion started by: lo-lp-kl
2 Replies
4. Post Here to Contact Site Administrators and Moderators
Hi Dumb question I know but I am new to this forum and have looked every where on this site but can not find "How to close" a thread I have posted....
Please advise on the procedures.
Thanks
Andrek (3 Replies)
ddi_can_receive_sig(9F) Kernel Functions for Drivers ddi_can_receive_sig(9F)NAME
ddi_can_receive_sig - Test for ability to receive signals
SYNOPSIS
#include <sys/ddi.h>
#include <sys/sunddi.h>
boolean_t ddi_can_receive_sig(void);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI).
PARAMETERS
None.
DESCRIPTION
The ddi_can_receive_sig() function returns a boolean value indicating whether the current thread can receive signals sent by kill(2).
If the return value is B_FALSE, then the calling thread cannot receive signals, and any call to qwait_sig(9F), cv_wait_sig(9F), or
cv_timedwait_sig(9F) implicitly becomes qwait(9F), cv_wait(9F), or cv_timedwait(9F), respectively. Drivers that can block indefinitely
awaiting an event should use this function to determine if additional means (such as timeout(9F)) may be necessary to avoid creating unkil-
lable threads.
RETURN VALUES
B_FALSE The calling thread is in a state in which signals cannot be received. For example, the thread is not
associated with a user process or is in the midst of exit(2) handling.
B_TRUE The calling thread may receive a signal while blocked on a condition variable. Note that this function
does not check to determine whether signals are blocked (see sigprocmask(2)).
CONTEXT
The ddi_can_receive_sig() function may be called from user, kernel, or interrupt context.
SEE ALSO close(9E), cv_wait(9F), qwait(9F)SunOS 5.10 15 Dec 2003 ddi_can_receive_sig(9F)