Not sure if this has been fixed in 6.1.a, but in 6.1.0 the rc.sysinit checks
for the non-existence of /dev/socket instead of the existence of /dev/socket
where it does the inetd start in the “Start some daemons” section. Also,
why isn’t inetd started by default? It isn’t as if the install doesn’t
install other things that people may not want to use, but inetd is probably
one of those programs that is used the most (IMO).
Jim
“Jim Lambert” <jlambert@futurex.com> wrote in message
news:a567i2$1j1$1@inn.qnx.com…
Not sure if this has been fixed in 6.1.a, but in 6.1.0 the rc.sysinit
checks
for the non-existence of /dev/socket instead of the existence of
/dev/socket
where it does the inetd start in the “Start some daemons” section. Also,
why isn’t inetd started by default? It isn’t as if the install doesn’t
install other things that people may not want to use, but inetd is
probably
one of those programs that is used the most (IMO).
Security issue I beleive. When inetd is started it becomes a lot more
vulnerable.
Jim
On Fri, 22 Feb 2002 15:27:04 -0500, “Mario Charest”
<goto@nothingness.com> wrote:
This is different than a security safeguard. The lines to start inetd
are commented out by default which keeps it from being started unless
you remove the comments. The problem is, once you do remove the
comments, it still won’t start because the script only tries to start
it if /dev/socket doesn’t exist, which is a mistake. It’s an easy
one to fix though, just change it from “if test ! -d…” to “if test
-d…” and it works fine.
I’m not sure if this is fixed in 6.1.0A or not. My QNX systems were
installed from a CD burned from an .iso image I d/led from QNX about a
month ago. The problem still existed with that install.
By the way, on a 6.1.0A system does ‘uname’ still report 6.1.0 or does
it report 6.1.0A?
C.
“Jim Lambert” <> jlambert@futurex.com> > wrote in message
news:a567i2$1j1$> 1@inn.qnx.com> …
Not sure if this has been fixed in 6.1.a, but in 6.1.0 the rc.sysinit
checks
for the non-existence of /dev/socket instead of the existence of
/dev/socket
where it does the inetd start in the “Start some daemons” section. Also,
why isn’t inetd started by default? It isn’t as if the install doesn’t
install other things that people may not want to use, but inetd is
probably
one of those programs that is used the most (IMO).Security issue I beleive. When inetd is started it becomes a lot more
vulnerable.
Jim
FWIW it’s definitely been fixed for 6.2
“Jim Lambert” <jlambert@futurex.com> wrote in message
news:a567i2$1j1$1@inn.qnx.com…
Not sure if this has been fixed in 6.1.a, but in 6.1.0 the rc.sysinit
checks
for the non-existence of /dev/socket instead of the existence of
/dev/socket
where it does the inetd start in the “Start some daemons” section. Also,
why isn’t inetd started by default? It isn’t as if the install doesn’t
install other things that people may not want to use, but inetd is
probably
one of those programs that is used the most (IMO).Jim
By the way, on a 6.1.0A system does ‘uname’ still report 6.1.0 or does
it report 6.1.0A?
6.1.0