Re: How do I find out the list of active network objects?

[Rob Davies <robdavies@worldnet.att.net>]

RE: Adding it back in the file 

Cool ... thanks ... you can get the same info from NCP from another node
(aka. $ mc ncp tell <nodename> show known object char ) so I don't think
it would be a big security risk ... of course, NCP doesn't tell you the
process names associated with the object unless you connect with privs,
it just tells you the objects it knows about, and if there is a process
ID associated with them (or 0 if the object was 'defined' in the NCP
database but doesn't have an attached process right now ... similar to
the way dnetd works).

>> There's no NCP support (yet ;-)), but if you have any other suggestions
>> on how I can find out this kind of information, that would be useful too
>> ...
>>
>From the actual applications themselves, you can use getsockopt() to get
>information on the state of the sockets. You can also use getsockname()
>to get the local socket address, and getpeername() to get the remote
>address.

Is there a way (without using /proc/net/decnet) to 'step through the
list' of active DECnet sockets and query the object name that is being
used? something like a 'getnextactivednsocket()' call ?

In the meantime, I'll take a look at the 'netstat' code to find out how
to add a new address family ... it does Netware IPX already, so I don't
see why we shouldn't just add DECnet to the options on the 'netstat -A
<family>' command.

Regards,

Rob.
-----------------------------------------------------------------------------
To unsubscribe from this list, send a mail to majordomo@dreamtime.org
containing the line "unsubscribe linux-decnet"
-----------------------------------------------------------------------------