On Wed, Jul 29, 2015 at 05:17:30PM +0100, Rainer Weikusat wrote:
> Isaac Dunham writes:
> > On Wed, Jul 29, 2015 at 01:21:04PM +0100, Rainer Weikusat wrote:
> >> Isaac Dunham writes:
> >> > Or you can do it with mount, sudo, sh, and nlmon
> >> > (http://git.r-36.net/nlmon).
> >>
> >> Using poll
Isaac Dunham writes:
> On Wed, Jul 29, 2015 at 01:21:04PM +0100, Rainer Weikusat wrote:
>> Isaac Dunham writes:
>> > Or you can do it with mount, sudo, sh, and nlmon
>> > (http://git.r-36.net/nlmon).
>>
>> Using poll to wait for a message followed by recvmsg for reading it
>> offers (in absence
On Wed, Jul 29, 2015 at 01:21:04PM +0100, Rainer Weikusat wrote:
> Isaac Dunham writes:
> > Or you can do it with mount, sudo, sh, and nlmon
> > (http://git.r-36.net/nlmon).
>
> Using poll to wait for a message followed by recvmsg for reading it
> offers (in absence of a timeout) no advantages o
Isaac Dunham writes:
> Or you can do it with mount, sudo, sh, and nlmon (http://git.r-36.net/nlmon).
Using poll to wait for a message followed by recvmsg for reading it
offers (in absence of a timeout) no advantages over just doing a
blocking recv. Since this code neither uses control messages no