SIGTTIN signal when running process in the background (ksh SunOS 5.6)

[stephan beal]

Stephane CHAZELAS wrote:

> to read(2) system calls. The libc scanf(3) function performs
> such calls.

<big snip>

> You can play around with "ps -j", perl -e 'iotcl(...', and the
> setsid(1) command (you may not have it) so see how things work.
>
> If you have a GNU system, look at: info -f libc -n 'Job Control'

Stephane,

Thanks. :)
i learned a lot from your post.

--
----- stephan beal
Registered Linux User #71917 [url]http://counter.li.org[/url]
I speak for myself, not my employer. Contents may
be hot. Slippery when wet. Reading disclaimers makes
you go blind. Writing them is worse. You have been Warned.

[Barry Margolin]

In article <c9b7e912.0307211108.5b20f536@posting.google.com >,
Gabriel <gabielex@hotmail.com> wrote:

>The funny thing is that I added some code to generate a core file when
>the signal SIGTTIN is catched, to see if I can find out what function
>call is triggering the signal. Well, compiled the code and now I can't
>reproduce the error again. It just seems to work fine running in the
>background. Weird.
>
>I've fixed some bugs in other parts of the code in the meantime so I
>don't know what may have affeced to this. Well, I'll let you know when
>(if) I find out.

Some ioctls on a terminal device will also signal SIGTTIN. Maybe you were
doing these to stdin, and your changes removed them.

--
Barry Margolin, [email]barry.margolin@level3.com[/email]
Level(3), Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.