From: mohit89mlnc@gmail.com (mohit verma)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Common signal handler system call
Date: Sat, 19 Mar 2011 02:42:26 +0530 [thread overview]
Message-ID: <AANLkTi=Mr1OmWSVwHZpugAWHphzTeFOF-sSMh0bR9L9S@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikJ1pZwrpn92sFeS9nCps0jL80GUeO-yWjkhwzd@mail.gmail.com>
On Sat, Mar 19, 2011 at 2:00 AM, Manish Katiyar <mkatiyar@gmail.com> wrote:
> On Fri, Mar 18, 2011 at 1:11 PM, mohit verma <mohit89mlnc@gmail.com>
> wrote:
> > Hi folks,
> > AFAIK there is not particular system call in Linux systems that can
> > register a number of signals (signal numbers) at once and provide a
> common
> > signal handler for all of the assembled signals.
>
> Did you try giving a common signal handler for two different signals ?
>
Yes i did.
>
> > I know doing this may be
> > hardly required in practice.
>
> Why not....for example... I want to print "quitting...." error msg if
> I get SIGINT or SIGQUIT.
>
Ok. i think these messages are for debugging purpose. But anyway let it be
common. :)
>
>
> > But i think this type of system call should be
> > in Linux systems which can serve handler functionality on some of
> signals.
> > Please tell me the flaws proposing something like this. i want to work on
> > this tiny problem. :)
> > --
> > ........................
> > MOHIT VERMA
> >
> >
> >
> > --
> > ........................
> > MOHIT VERMA
> >
> > _______________________________________________
> > Kernelnewbies mailing list
> > Kernelnewbies at kernelnewbies.org
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> >
> >
>
>
>
> --
> Thanks -
> Manish
>
--
........................
*MOHIT VERMA*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110319/4f887c4c/attachment-0002.html
next prev parent reply other threads:[~2011-03-18 21:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 19:54 Common signal handler system call mohit verma
2011-03-18 20:02 ` Fwd: " mohit verma
2011-03-18 20:11 ` mohit verma
2011-03-18 20:30 ` Manish Katiyar
2011-03-18 21:12 ` mohit verma [this message]
2011-03-19 11:31 ` Bernd Petrovitsch
2011-03-19 14:18 ` mohit verma
2011-03-19 21:43 ` Bernd Petrovitsch
2011-03-20 7:38 ` mohit verma
2011-03-20 14:57 ` Javier Martinez Canillas
2011-03-21 10:38 ` Bernd Petrovitsch
2011-03-21 12:16 ` mohit verma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=Mr1OmWSVwHZpugAWHphzTeFOF-sSMh0bR9L9S@mail.gmail.com' \
--to=mohit89mlnc@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).