/usr/sbin/inetd - starting automatically

How do I start the ftp services in inetd.conf? Where do I insert a line like exec /usr/sbin/inetd? In one of the startup scripts? Which one?

Somewhere in your script after the io-net call.

io-net -d -p
ifconfig or netmanager (must have net.cfg)
inetd &

/etc/inetd.conf and /etc/services should be OK.

If this isn’t an embedded application of QNX, then you want to add your line in /etc/rc.d/rc.local. If the rc.local doesn’t currently exist, simply create it in this /etc/rc.d directory.

Ok, I was able to get the like “Starting extra run commands” to come up by doing a chmod +x rc.local. This was after I read the rc.sysinit script.

Ok, now it looks like its hung. Are you sure I was supposed to use an exec? I’m not sure I was supposed to.

nobody suggested using “exec” :slight_smile:
you just need to put
/usr/sbin/inetd &
in your /etc/rc.d/rc.local file and make sure it is executable.

Now, if you use “exec” in rc.local, your startup progress will stop after that, and you will NOT be able to get the login screen. Basically, it will look like “hang”.

You can boot from CD and “fix” your rc.local file. Or, you can boot your system into “debug shell” mode: press “Spacebar” during booting up, then hit “F5” for the debug shell. Once you are in debug shell (a.k.a “fesh”), you will have some limited commands available, such as “els”, “ecp”, “erm”, and “cd”. so you can
cd /etc/rc.d
els
ecp rc.local rc.local.bad
erm rc.local
now you should be ok.

Thanks to all who helped. The machine now lets me shell into it when it boots.
I’m new to qnx and mostly worked in embedded platforms before. QNX looks to be very interesting - but expensive if you want to make a product out of it.

The price really depends on volumes. If you are only make 5-10 device a year the cost of those devices would have to be very high and the relative cost of QNX is generally not significant.

Or do you mean for a development seat?