Problem with SP2, mpc85x0ads BSP and inetd

QNX Newsgroups (Archives) qnx.bsp
1

I installed SP2 and ported my QNX System Builder project to the new Momentics.
I also installed the patch for the ne TCP/IP stack [Patch ID 97].
Everything works fine except inetd which exits just after been launched with “exit status 0”.

I looked in documentation and didn’t find any difference between SP1 and SP2 for inetd.

Any idea?

Armand

2

Armand Ciejak <armand.ciejak@free.fr> wrote:

I installed SP2 and ported my QNX System Builder project to the new Momentics.
I also installed the patch for the ne TCP/IP stack [Patch ID 97].
Everything works fine except inetd which exits just after been launched with “exit status 0”.

I looked in documentation and didn’t find any difference between SP1 and SP2 for inetd.

Any idea?

Armand

It forks and exits do daemonize itself but the child should
stay around. Is it actually missing from any ‘pidin’ output?


-seanb

3

Sean Boudreau wrote:

Armand Ciejak <> armand.ciejak@free.fr> > wrote:

I installed SP2 and ported my QNX System Builder project to the new Momentics.
I also installed the patch for the ne TCP/IP stack [Patch ID 97].
Everything works fine except inetd which exits just after been launched with “exit status 0”.


I looked in documentation and didn’t find any difference between SP1 and SP2 for inetd.


Any idea?


Armand


It forks and exits do daemonize itself but the child should
stay around. Is it actually missing from any ‘pidin’ output?

I can not see any inetd in the pidin output.
If I try to open a telnet session (QNX beeing the server) the telnet client says: connection
refused. With SP1 it worked perfectly!

-seanb

4

Can you do an “inetd -d” to see what’s going on?

-xtang

Armand Ciejak <armand.ciejak@free.fr> wrote:

Sean Boudreau wrote:
Armand Ciejak <> armand.ciejak@free.fr> > wrote:

I installed SP2 and ported my QNX System Builder project to the new Momentics.
I also installed the patch for the ne TCP/IP stack [Patch ID 97].
Everything works fine except inetd which exits just after been launched with “exit status 0”.


I looked in documentation and didn’t find any difference between SP1 and SP2 for inetd.


Any idea?


Armand


It forks and exits do daemonize itself but the child should
stay around. Is it actually missing from any ‘pidin’ output?

I can not see any inetd in the pidin output.
If I try to open a telnet session (QNX beeing the server) the telnet client says: connection
refused. With SP1 it worked perfectly!



-seanb

5

Here is the results:

inetd → nothing happen, no error message, no inetd in pidin output
inetd -d → nothing happen, no error message, no inetd in pidin output
inetd & → “exited with status 0”
inetd -d & → “exited with status 255”

/etc/inetd.conf, /etc/services and /etc/passwd are the same as with SP1

The rest is working normaly; qconn, my applications, …

Armand

xtang@qnx.com wrote:

Can you do an “inetd -d” to see what’s going on?

-xtang

Armand Ciejak <> armand.ciejak@free.fr> > wrote:

Sean Boudreau wrote:

Armand Ciejak <> armand.ciejak@free.fr> > wrote:


I installed SP2 and ported my QNX System Builder project to the new Momentics.
I also installed the patch for the ne TCP/IP stack [Patch ID 97].
Everything works fine except inetd which exits just after been launched with “exit status 0”.


I looked in documentation and didn’t find any difference between SP1 and SP2 for inetd.


Any idea?


Armand


It forks and exits do daemonize itself but the child should
stay around. Is it actually missing from any ‘pidin’ output?

I can not see any inetd in the pidin output.
If I try to open a telnet session (QNX beeing the server) the telnet client says: connection
refused. With SP1 it worked perfectly!



-seanb

6

What is the user name when you telnet? If the user name has a dot ‘.’ in
it like armand.ciejak (as your e-mail suggests) then try w/o the dot.
When we moved from 6.1 to 6.2.x we had to remove ‘.’ from user names.

Cheers,
-Dmitri

Armand Ciejak wrote:

Here is the results:

inetd → nothing happen, no error message, no inetd in pidin output
inetd -d → nothing happen, no error message, no inetd in pidin output
inetd & → “exited with status 0”
inetd -d & → “exited with status 255”

/etc/inetd.conf, /etc/services and /etc/passwd are the same as with SP1

The rest is working normaly; qconn, my applications, …

Armand

xtang@qnx.com > wrote:

Can you do an “inetd -d” to see what’s going on?

-xtang

Armand Ciejak <> armand.ciejak@free.fr> > wrote:

Sean Boudreau wrote:

Armand Ciejak <> armand.ciejak@free.fr> > wrote:


I installed SP2 and ported my QNX System Builder project to the new
Momentics.
I also installed the patch for the ne TCP/IP stack [Patch ID 97].
Everything works fine except inetd which exits just after been
launched with “exit status 0”.



I looked in documentation and didn’t find any difference between
SP1 and SP2 for inetd.



Any idea?



Armand



It forks and exits do daemonize itself but the child should
stay around. Is it actually missing from any ‘pidin’ output?


I can not see any inetd in the pidin output.
If I try to open a telnet session (QNX beeing the server) the telnet
client says: connection refused. With SP1 it worked perfectly!



-seanb

7

It’s not a problem with user name, since it’s not possible to run the server.

Dmitri Poustovalov wrote:

What is the user name when you telnet? If the user name has a dot ‘.’ in
it like armand.ciejak (as your e-mail suggests) then try w/o the dot.
When we moved from 6.1 to 6.2.x we had to remove ‘.’ from user names.

Cheers,
-Dmitri

Armand Ciejak wrote:

Here is the results:

inetd → nothing happen, no error message, no inetd in pidin output
inetd -d → nothing happen, no error message, no inetd in pidin output
inetd & → “exited with status 0”
inetd -d & → “exited with status 255”

/etc/inetd.conf, /etc/services and /etc/passwd are the same as with SP1

The rest is working normaly; qconn, my applications, …

Armand

xtang@qnx.com > wrote:

Can you do an “inetd -d” to see what’s going on?

-xtang

Armand Ciejak <> armand.ciejak@free.fr> > wrote:

Sean Boudreau wrote:

Armand Ciejak <> armand.ciejak@free.fr> > wrote:


I installed SP2 and ported my QNX System Builder project to the
new Momentics.
I also installed the patch for the ne TCP/IP stack [Patch ID 97].
Everything works fine except inetd which exits just after been
launched with “exit status 0”.




I looked in documentation and didn’t find any difference between
SP1 and SP2 for inetd.




Any idea?




Armand




It forks and exits do daemonize itself but the child should
stay around. Is it actually missing from any ‘pidin’ output?



I can not see any inetd in the pidin output.
If I try to open a telnet session (QNX beeing the server) the telnet
client says: connection refused. With SP1 it worked perfectly!



-seanb

8

The problem was that the config files were in DOS format :frowning:

Armand

Armand Ciejak wrote:

It’s not a problem with user name, since it’s not possible to run the
server.

Dmitri Poustovalov wrote:

What is the user name when you telnet? If the user name has a dot ‘.’
in it like armand.ciejak (as your e-mail suggests) then try w/o the
dot. When we moved from 6.1 to 6.2.x we had to remove ‘.’ from user
names.

Cheers,
-Dmitri

Armand Ciejak wrote:

Here is the results:

inetd → nothing happen, no error message, no inetd in pidin output
inetd -d → nothing happen, no error message, no inetd in pidin output
inetd & → “exited with status 0”
inetd -d & → “exited with status 255”

/etc/inetd.conf, /etc/services and /etc/passwd are the same as with SP1

The rest is working normaly; qconn, my applications, …

Armand

xtang@qnx.com > wrote:

Can you do an “inetd -d” to see what’s going on?

-xtang

Armand Ciejak <> armand.ciejak@free.fr> > wrote:

Sean Boudreau wrote:

Armand Ciejak <> armand.ciejak@free.fr> > wrote:


I installed SP2 and ported my QNX System Builder project to the
new Momentics.
I also installed the patch for the ne TCP/IP stack [Patch ID 97].
Everything works fine except inetd which exits just after been
launched with “exit status 0”.





I looked in documentation and didn’t find any difference between
SP1 and SP2 for inetd.





Any idea?





Armand





It forks and exits do daemonize itself but the child should
stay around. Is it actually missing from any ‘pidin’ output?




I can not see any inetd in the pidin output.
If I try to open a telnet session (QNX beeing the server) the
telnet client says: connection refused. With SP1 it worked perfectly!



-seanb