I start Net, Net.driver for the hardware NIC I have on the machine, and
Tcpip - from the /etc/config/sysinit.$NODE.
If I start Net.fd from the user shell later on - Tcpip does not notice the
new device. How to inform the socket server about it?
Tony.
PS
Sending “kill -SIGHUP <Tcpip’s pid>” crashes the system dead…
Tony <mts.spb.suxx@mail.ru> wrote:
I start Net, Net.driver for the hardware NIC I have on the machine, and
Tcpip - from the /etc/config/sysinit.$NODE.If I start Net.fd from the user shell later on - Tcpip does not notice the
new device. How to inform the socket server about it?
I don’t know of anyway to inform socket about a Net.driver that is
started after Socket or Tcpip has been started.
If you need TCP/IP accross a serial connection, but don’t actually
need QNX messaging, I think the usual way would be PPP (or SLIP).
If you need both QNX messaging and TCP/IP accross that same serial
connection, then I don’t know a way to do that after startup.
PS
Sending “kill -SIGHUP <Tcpip’s pid>” crashes the system dead…
That probably shouldn’t happen. That is, it shouldn’t crash the
system dead, but Tcpip will not take a SIGHUP as a “reconfig” the
way that inetd (for example) does.
David Gibbs
QNX Training Services
dagibbs@qnx.com
David Gibbs <dagibbs@qnx.com> wrote:
Tony <> mts.spb.suxx@mail.ru> > wrote:
PS
Sending “kill -SIGHUP <Tcpip’s pid>” crashes the system dead…That probably shouldn’t happen. That is, it shouldn’t crash the
system dead, but Tcpip will not take a SIGHUP as a “reconfig” the
way that inetd (for example) does.
Tried this on my system, btw, and Tcpip went away, but rest of my
system survived fine.
Might be fixed, might be a configuration difference in what triggers
the system going down.
David Gibbs
QNX Training Services
dagibbs@qnx.com