tx_down failed ENOBUFS

Yeah, I seriously considered that several times; but I was desperately hoping that there was some
undocumented way to get a look inside without having to go to that extreme. We’re still having
some difficulty figuring out the whole io-net/mount relationship - I was surprised, for instance,
that globals in io-net are not visible to mounted drivers. My first thought was “How did they do
THAT?!”

Also, we’ve already been bitten several times by the fact that the source we can obtain doesn’t
necessarily match the source from which the shipping product is built. And when you’re searching
for an elusive bug, changing the environment in an unknown way is the last thing you want to do!

But thanks for the tips! They got me thinking in the right direction.

Murf

Sean Boudreau wrote:

John A. Murphy <> murf@perftech.com> > wrote:
Once again, it sure would have been
helpful to be able to observe the io-net interals, and see that the counter had gone negative
instead of bumping into the limit.

OK I’ll bite. Since you appear to have the source, you could have
built your own io-net and debugged it accordingly.

-seanb

John A. Murphy <murf@perftech.com> wrote:

Yeah, I seriously considered that several times; but I was desperately
hoping that there was some undocumented way to get a look inside
without having to go to that extreme. We’re still having some
difficulty figuring out the whole io-net/mount relationship - I was
surprised, for instance, that globals in io-net are not visible to
mounted drivers. My first thought was “How did they do THAT?!”

Good point.

Sorry to interrupt the thread. I’m just starting to get into the real
guts of resource managers. I’d like a better description of the
interface between ‘mount’ and a resorce manager. Especially with
regard to mounting libraries to a running process.

For instance, how does mount know which resource manager you are
dealing with? Are names like ‘io-net’ hard coded into the mount
command? I assume not.

Does mount just look for the argument to -T to be the name of an
executable? If so, what if there is more than one instance of that
executable running?