How should I interpret pidin returning “couldn’t fill_info”.
- Mario
Mario Charest <mcharest@antispam_zinformatic.com> wrote:
How should I interpret pidin returning “couldn’t fill_info”.
I guess the process went away between pidin finding that process
and querying the info of that process.
“Colin Burgess” <cburgess@qnx.com> wrote in message
news:98bek3$a81$2@nntp.qnx.com…
Mario Charest <mcharest@antispam_zinformatic.com> wrote:
How should I interpret pidin returning “couldn’t fill_info”.I guess the process went away between pidin finding that process
and querying the info of that process.
Hum I doubt that’s the problem in my case. I get about
20 of them and everytime I run pidin. That being said
I’m attemping to remotely boot across qnet, I haven’t
found an easy way and i’m having problem with qnet
itself. So maybe entries under /proc are somewhat
corrupted.
The message is just pidin’s way to tell you that devctl(DCMD_PROC_…) has
failed. I don’t think they ever anticipated it being actually printed so it
sounds funny. But fear not, I’ve seen more eloquent output from QNX
software, like ‘Oh, crap! Funky stuff happening!’. Then I was told the
author of that part was Irish 
Even if pidin printed errno its value might not be very useful in this case
I’m afraid. In my experience this can happen if you execute pidin very
often. My wild guess would be some race condition in the procfs.
- igor
“Mario Charest” <mcharest@void_zinformatic.com> wrote in message
news:98c6nr$nij$1@nntp.qnx.com…
“Colin Burgess” <> cburgess@qnx.com> > wrote in message
news:98bek3$a81$> 2@nntp.qnx.com> …
Mario Charest <mcharest@antispam_zinformatic.com> wrote:
How should I interpret pidin returning “couldn’t fill_info”.I guess the process went away between pidin finding that process
and querying the info of that process.Hum I doubt that’s the problem in my case. I get about
20 of them and everytime I run pidin. That being said
I’m attemping to remotely boot across qnet, I haven’t
found an easy way and i’m having problem with qnet
itself. So maybe entries under /proc are somewhat
corrupted.
\