04-18-2020
Dear hicksd8,
Yes, My initial PM to him only. He suggest me raise new discussion referring old post.
Its better if we hide it completely with dummy values.
However, thanks for your prompt action to move it to member only.
Last edited by hicksd8; 04-19-2020 at 08:49 AM..
5 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
I am unable to open the mimesender thread. I get the following message when clicking on https://www.unix.com/showthread.php?p=33233#post33233 : (2 Replies)
Discussion started by: dangral
2 Replies
2. Post Here to Contact Site Administrators and Moderators
I've made the thread title as descriptive as possible since I don't know if the admins can open it.
Well sure, now I can open THIS one. I'm getting it on any other thread I try in What's On Your Mind and High Level Programming.
Okay, it's decided to make a liar of me now. It seems to be... (2 Replies)
Discussion started by: Corona688
2 Replies
3. Post Here to Contact Site Administrators and Moderators
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)
Discussion started by: enriquegm82
1 Replies
4. Post Here to Contact Site Administrators and Moderators
Hi,
I've just posted a new thread on the "IP Networking" subforum, with the subject "Check connectivity with multiple hosts - BASH script available here".
However, I think it should be on the "Shell Programming and Scripting" subforum, could you please move that thread there?
Thanks! (1 Reply)
Discussion started by: Fr3dY
1 Replies
5. Post Here to Contact Site Administrators and Moderators
Dear colleagues,
this post doesn't open; error message:
Anything we / I can do?
Rgds
Rüdiger (0 Replies)
Discussion started by: RudiC
0 Replies
LEARN ABOUT DEBIAN
gsignal
GSIGNAL(3) Linux Programmer's Manual GSIGNAL(3)
NAME
gsignal, ssignal - software signal facility
SYNOPSIS
#include <signal.h>
typedef void (*sighandler_t)(int);
int gsignal(int signum);
sighandler_t ssignal(int signum, sighandler_t action);
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
gsignal(), ssignal(): _SVID_SOURCE
DESCRIPTION
Don't use these functions under Linux. Due to a historical mistake, under Linux these functions are aliases for raise(3) and signal(2),
respectively.
Elsewhere, on System V-like systems, these functions implement software signaling, entirely independent of the classical signal(2) and
kill(2) functions. The function ssignal() defines the action to take when the software signal with number signum is raised using the func-
tion gsignal(), and returns the previous such action or SIG_DFL. The function gsignal() does the following: if no action (or the action
SIG_DFL) was specified for signum, then it does nothing and returns 0. If the action SIG_IGN was specified for signum, then it does noth-
ing and returns 1. Otherwise, it resets the action to SIG_DFL and calls the action function with argument signum, and returns the value
returned by that function. The range of possible values signum varies (often 1-15 or 1-17).
CONFORMING TO
These functions are available under AIX, DG/UX, HP-UX, SCO, Solaris, Tru64. They are called obsolete under most of these systems, and are
broken under Linux libc and glibc. Some systems also have gsignal_r() and ssignal_r().
SEE ALSO
kill(2), signal(2), raise(3)
COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
2007-07-26 GSIGNAL(3)