Very Computer

by **Thomas Leye** » Tue, 26 Sep 2000 04:00:00

Hi there,

could anybody explain to me, why it ist possible, to
push a STREAMS-module (e.g. dedump) on my actual shell,
but when I push it onto /dev/tcp, neither strconf is
able to see it, nor is there any output from this module...

It's mentioned in modinfo-output.

Is it possible, that this is part of the device-cloning
method?

Thanks

Thomas

by **Andrew Gabri** » Tue, 26 Sep 2000 04:00:00

Quote:
> Hi there,

> could anybody explain to me, why it ist possible, to
> push a STREAMS-module (e.g. dedump) on my actual shell,

Sorry, I didn't understand that.

Quote:> but when I push it onto /dev/tcp, neither strconf is
> able to see it, nor is there any output from this module...

When you push it onto tcp, it exists only on the stream on
which it was pushed. Other applications opening streams
to tcp (such as strconf) won't have it on their streams.

Quote:> It's mentioned in modinfo-output.

That means something pushed it at some time in the past and it's
either still in use, or the kernel hasn't needed to unload any
unused modules since it was last used.

Quote:> Is it possible, that this is part of the device-cloning
> method?

Yes. I suspect that if you pushed it onto a non-cloned device,
strconf would see it, as it would be using the same stream.
However, I haven't actually tried this.

--
Andrew Gabriel

by **Ingo Dahm - SAP-Sun CC Walldor** » Wed, 27 Sep 2000 15:23:55

Quote:> > but when I push it onto /dev/tcp, neither strconf is
> > able to see it, nor is there any output from this module...

check your /var/adm/messages

Cheers,

-ingo

------------------------------------------------------------------
Ingo Dahm Sun Microsystems Inc - MDE
Global SAP-Sun CC
Altrottstr. 31
69190 Walldorf, Germany

Phone: +49-6227-356-233
+49-6227-7-43454
Fax: +49-6227-356-209
+49-6227-356-222

Very Computer

STREAMS: push module on /dev/tcp

STREAMS: push module on /dev/tcp

STREAMS: push module on /dev/tcp

STREAMS: push module on /dev/tcp