Re: setting timer
loic-dev_at_gmx.net
Date: 07/06/05
- Next message: tachoknight_at_gmail.com: "Missing shared library when run as daemon"
- Previous message: Torsten Mueller: "Re: Make File"
- In reply to: James Antill: "Re: setting timer"
- Next in thread: loic-dev_at_gmx.net: "Re: setting timer"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 6 Jul 2005 08:51:22 -0700
> > Well that would be a bit restrictive, actually. You can also call the
> > so-called async-signal-safe functions. The list can be found in SUS,
> > here copied below for your convenience.
>
> Kind of, while these are "safe" there are a lot of unsafe cases. For
> instance close() is "safe" ... but if you close an fd you are using in
> your main application code, you can pretty much guarantee the code is
> unsafe.
This definition of safe has a particular meaning, namely the meaning of
SUSv3. It must be understood like "*If* you do the thing *correctly*,
then it is safe".
That's the same with multi-threading. close() is thread-safe, but if
you close an fd that you are using later in an other thread, then you
will likely have some troubles. But you are not suppose to close an fd
that you are using later, are you?
Regards,
Loic.
- Next message: tachoknight_at_gmail.com: "Missing shared library when run as daemon"
- Previous message: Torsten Mueller: "Re: Make File"
- In reply to: James Antill: "Re: setting timer"
- Next in thread: loic-dev_at_gmx.net: "Re: setting timer"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|