tech-kern archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: flock(2): locking against itself?
>> Another option is to use newterm() in curses with a funopen()ed
>> stream for output which queues the output to be written
>> (nonblockingly) to the real stdout.
> Would toggling O_NONBLOCK using fcntl() work for you? A bit tedious,
> but it can be done "per operation".
...ish. I hadn't thought of that. But, the way the code is
structured, that actually isn't a crazy suggestion at all.
I'm not sure it would work, but it's a very good thought.
Thank you!
Mouse
Home |
Main Index |
Thread Index |
Old Index