We use QNX 1 on our test machines at work. One of the machines crashed and on reboot suffered from a loss of network connectivity.
When trying to use the ping command, I get the following error
“ping: socket: invalid argument”. Similar messages are seen for ftp.
Tried a new OS and application image and it works fine, so we know its the software installation thats the issue. Looking for some pointers on how to determine where the corruption could lie.
We use QNX 4.22 on our test machines at work. One of the machines crashed and on reboot suffered from a loss of network connectivity.
When trying to use the ping command, I get the following error
“ping: socket: invalid argument”. Similar messages are seen for ftp.
Tried a new OS and application image and the setup then works fine, so we know its the software installation thats the issue. Looking for some pointers on how to determine where the corruption could lie.
I think forums and newsgroups causing ppl do not think. They are searching help everywhere, instead of trying to solve it, e.g. compare output of ‘pidin’ or ‘ps’ on two machines and compare, it’s trivial, isn’t it ?
Nice to see you lestat, your QOpenCD project must be very successful now that QSS is not doing anything in that area
getshorty1965, have you checked the Socket (or Socklet) to see if they are running as lestat suggested? or compare the process list of the two computers to see what’s different. This should at least get you started. The error you posted seem to indicate tcpip stack is not running.
At the last QNX convention, at least the last one I attended, I loan QSSL an IBM PC and my copies of QNX version .43. It still works just like new, but doesn’t have quite as many features as later versions.