Can anyone tell me how to view System Information (RAM, processor speed,
hard drive size, etc) on a QNX machine?
I was able to find the IDE System Information option but have not been able
to configure the target so that it actually works. I’ve entered the IP
address but, no matter what other options I pick, I always get a “not
connected” message - when I know for a fact that the unit IS connected.
Help?
-laura j.
Laura Jones wrote:
Can anyone tell me how to view System Information (RAM, processor speed,
hard drive size, etc) on a QNX machine?
Type “sin info” on the target, that’ll return node name, RAM size,
processor speed and processor name. “df -kP” on the target will list
drives along with user/free space, etc.
I was able to find the IDE System Information option but have not been able
to configure the target so that it actually works. I’ve entered the IP
address but, no matter what other options I pick, I always get a “not
connected” message - when I know for a fact that the unit IS connected.
Is qconn running on the target machine? Without it, the System
Information perspective can’t collect any data (and most other IDE
features won’t work with the target, either).
–
Chris Herborth (cherborth@qnx.com) - Senior Zombiologist and Tech Writer
Never send a monster to do the work of an evil scientist.
Monthly QNX newsletter - http://www.qnx.com/news/forms/newsletter.html
I don’t know. I don’t know what qconn is or how to check for it.
fyi: I inherited this machine with a new job but, unfortunately, no
training. Our 2 QNX programmers have not be available (and possibly don’t
have the knowledge) to help me.
-laura j.
“Chris Herborth” <cherborth@qnx.com> wrote in message
news:dune7g$a1k$1@inn.qnx.com…
Laura Jones wrote:
Can anyone tell me how to view System Information (RAM, processor speed,
hard drive size, etc) on a QNX machine?Type “sin info” on the target, that’ll return node name, RAM size,
processor speed and processor name. “df -kP” on the target will list
drives along with user/free space, etc.I was able to find the IDE System Information option but have not been
able
to configure the target so that it actually works. I’ve entered the IP
address but, no matter what other options I pick, I always get a “not
connected” message - when I know for a fact that the unit IS connected.Is qconn running on the target machine? Without it, the System
Information perspective can’t collect any data (and most other IDE
features won’t work with the target, either).–
Chris Herborth (> cherborth@qnx.com> ) - Senior Zombiologist and Tech Writer
Never send a monster to do the work of an evil scientist.
Monthly QNX newsletter - > http://www.qnx.com/news/forms/newsletter.html
Laura Jones wrote:
I don’t know. I don’t know what qconn is or how to check for it.
fyi: I inherited this machine with a new job but, unfortunately, no
training. Our 2 QNX programmers have not be available (and possibly don’t
have the knowledge) to help me.
-laura j.
“Chris Herborth” <> cherborth@qnx.com> > wrote in message
news:dune7g$a1k$> 1@inn.qnx.com> …Laura Jones wrote:
Can anyone tell me how to view System Information (RAM, processor speed,
hard drive size, etc) on a QNX machine?Type “sin info” on the target, that’ll return node name, RAM size,
processor speed and processor name. “df -kP” on the target will list
drives along with user/free space, etc.
I was able to find the IDE System Information option but have not beenable
to configure the target so that it actually works. I’ve entered the IP
address but, no matter what other options I pick, I always get a “not
connected” message - when I know for a fact that the unit IS connected.Is qconn running on the target machine? Without it, the System
Information perspective can’t collect any data (and most other IDE
features won’t work with the target, either).–
Chris Herborth (> cherborth@qnx.com> ) - Senior Zombiologist and Tech Writer
Never send a monster to do the work of an evil scientist.
Monthly QNX newsletter - > http://www.qnx.com/news/forms/newsletter.html
use the ‘pidin’ command on your QNX target (at a command shell) to get a
listing of running processes. If qconn is not listed, then start it.
-Joe
the list of running processes was very long and scrolled over several pages.
is there a way to limit the view to the window?
assuming qconn is not running, how do i start it?
-laura j
“Joe Mammone” <hw@qnx.com> wrote in message news:dunhjs$c5d$1@inn.qnx.com…
Laura Jones wrote:
I don’t know. I don’t know what qconn is or how to check for it.fyi: I inherited this machine with a new job but, unfortunately, no
training. Our 2 QNX programmers have not be available (and possibly
don’t
have the knowledge) to help me.
-laura j.
“Chris Herborth” <> cherborth@qnx.com> > wrote in message
news:dune7g$a1k$> 1@inn.qnx.com> …Laura Jones wrote:
Can anyone tell me how to view System Information (RAM, processor
speed,
hard drive size, etc) on a QNX machine?Type “sin info” on the target, that’ll return node name, RAM size,
processor speed and processor name. “df -kP” on the target will list
drives along with user/free space, etc.
I was able to find the IDE System Information option but have not beenable
to configure the target so that it actually works. I’ve entered the IP
address but, no matter what other options I pick, I always get a “not
connected” message - when I know for a fact that the unit IS connected.Is qconn running on the target machine? Without it, the System
Information perspective can’t collect any data (and most other IDE
features won’t work with the target, either).–
Chris Herborth (> cherborth@qnx.com> ) - Senior Zombiologist and Tech Writer
Never send a monster to do the work of an evil scientist.
Monthly QNX newsletter - > http://www.qnx.com/news/forms/newsletter.html
use the ‘pidin’ command on your QNX target (at a command shell) to get a
listing of running processes. If qconn is not listed, then start it.-Joe
I tried loggin in as root, and typing qconn. Rec’d the following:
sh: qnconn: not found
-lj
“Joe Mammone” <hw@qnx.com> wrote in message news:dunhjs$c5d$1@inn.qnx.com…
Laura Jones wrote:
I don’t know. I don’t know what qconn is or how to check for it.fyi: I inherited this machine with a new job but, unfortunately, no
training. Our 2 QNX programmers have not be available (and possibly
don’t
have the knowledge) to help me.
-laura j.
“Chris Herborth” <> cherborth@qnx.com> > wrote in message
news:dune7g$a1k$> 1@inn.qnx.com> …Laura Jones wrote:
Can anyone tell me how to view System Information (RAM, processor
speed,
hard drive size, etc) on a QNX machine?Type “sin info” on the target, that’ll return node name, RAM size,
processor speed and processor name. “df -kP” on the target will list
drives along with user/free space, etc.
I was able to find the IDE System Information option but have not beenable
to configure the target so that it actually works. I’ve entered the IP
address but, no matter what other options I pick, I always get a “not
connected” message - when I know for a fact that the unit IS connected.Is qconn running on the target machine? Without it, the System
Information perspective can’t collect any data (and most other IDE
features won’t work with the target, either).–
Chris Herborth (> cherborth@qnx.com> ) - Senior Zombiologist and Tech Writer
Never send a monster to do the work of an evil scientist.
Monthly QNX newsletter - > http://www.qnx.com/news/forms/newsletter.html
use the ‘pidin’ command on your QNX target (at a command shell) to get a
listing of running processes. If qconn is not listed, then start it.-Joe
What version of QNX is installed on you target system? At the shell try
the following:
qconn should be under /usr/sbin
Check out the QNX System Architecture Guide and the Neutrino Users
Guide…these docs contain a lot of good info that will help you get up
to speed with QNX. The docs are available on the QNX website:
http://www.qnx.com/developers/docs/6.3.0SP2/momentics/bookset.html
-Joe
Laura Jones wrote:
I tried loggin in as root, and typing qconn. Rec’d the following:
sh: qnconn: not found-lj
“Joe Mammone” <> hw@qnx.com> > wrote in message news:dunhjs$c5d$> 1@inn.qnx.com> …Laura Jones wrote:
I don’t know. I don’t know what qconn is or how to check for it.
fyi: I inherited this machine with a new job but, unfortunately, no
training. Our 2 QNX programmers have not be available (and possiblydon’t
have the knowledge) to help me.
-laura j.
“Chris Herborth” <> cherborth@qnx.com> > wrote in message
news:dune7g$a1k$> 1@inn.qnx.com> …
Laura Jones wrote:
Can anyone tell me how to view System Information (RAM, processorspeed,
hard drive size, etc) on a QNX machine?
Type “sin info” on the target, that’ll return node name, RAM size,
processor speed and processor name. “df -kP” on the target will list
drives along with user/free space, etc.
I was able to find the IDE System Information option but have not beenable
to configure the target so that it actually works. I’ve entered the IP
address but, no matter what other options I pick, I always get a “not
connected” message - when I know for a fact that the unit IS connected.Is qconn running on the target machine? Without it, the System
Information perspective can’t collect any data (and most other IDE
features won’t work with the target, either).–
Chris Herborth (> cherborth@qnx.com> ) - Senior Zombiologist and Tech Writer
Never send a monster to do the work of an evil scientist.
Monthly QNX newsletter - > http://www.qnx.com/news/forms/newsletter.html
use the ‘pidin’ command on your QNX target (at a command shell) to get a
listing of running processes. If qconn is not listed, then start it.-Joe
Laura Jones wrote:
I don’t know. I don’t know what qconn is or how to check for it.
qconn is a conduit that the IDE uses for collecting data from the target
system. “pidin | grep qconn” will tell you if it’s running or not… if
not, you can launch it with “/usr/sbin/qconn”.
You can add “/usr/sbin/qconn” to your /etc/rc.d/rc.local file to have it
launched every time the system boots, too… note that this is a
security risk, so don’t leave it running on deployed systems.
–
Chris Herborth (cherborth@qnx.com) - Senior Zombiologist and Tech Writer
Never send a monster to do the work of an evil scientist.
Monthly QNX newsletter - http://www.qnx.com/news/forms/newsletter.html
Laura Jones wrote:
the list of running processes was very long and scrolled over several pages.
is there a way to limit the view to the window?
pidin | less
–
Chris Herborth (cherborth@qnx.com) - Senior Zombiologist and Tech Writer
Never send a monster to do the work of an evil scientist.
Monthly QNX newsletter - http://www.qnx.com/news/forms/newsletter.html
I’m running QNX 6.2.0. The target system is my own machine.
qconfig = sh: qconfig: not found
pidin | qrep qconn = sh: qrep: not found
/usr/sbin/qconn = nothing - returned to the # prompt (better than an error).
When I went to IDE System Information, my machine was still “not connected”
sin info provided Hard Drive, Host Name, and CPU info - but I’m still unable
to determine RAM.
-laura j.
“Chris Herborth” <cherborth@qnx.com> wrote in message
news:dupia1$nmm$1@inn.qnx.com…
Laura Jones wrote:
I don’t know. I don’t know what qconn is or how to check for it.qconn is a conduit that the IDE uses for collecting data from the target
system. “pidin | grep qconn” will tell you if it’s running or not… if
not, you can launch it with “/usr/sbin/qconn”.You can add “/usr/sbin/qconn” to your /etc/rc.d/rc.local file to have it
launched every time the system boots, too… note that this is a
security risk, so don’t leave it running on deployed systems.–
Chris Herborth (> cherborth@qnx.com> ) - Senior Zombiologist and Tech Writer
Never send a monster to do the work of an evil scientist.
Monthly QNX newsletter - > http://www.qnx.com/news/forms/newsletter.html
Ok…6.2.0 didn’t have the qconfig util so you are ok there.
The second error is a typo, replace qrep with grep.
Use ‘pidin info’, rather then sin
-Joe
Laura Jones wrote:
I’m running QNX 6.2.0. The target system is my own machine.
qconfig = sh: qconfig: not found
pidin | qrep qconn = sh: qrep: not found
/usr/sbin/qconn = nothing - returned to the # prompt (better than an error).
When I went to IDE System Information, my machine was still “not connected”sin info provided Hard Drive, Host Name, and CPU info - but I’m still unable
to determine RAM.-laura j.
“Chris Herborth” <> cherborth@qnx.com> > wrote in message
news:dupia1$nmm$> 1@inn.qnx.com> …Laura Jones wrote:
I don’t know. I don’t know what qconn is or how to check for it.
qconn is a conduit that the IDE uses for collecting data from the target
system. “pidin | grep qconn” will tell you if it’s running or not… if
not, you can launch it with “/usr/sbin/qconn”.You can add “/usr/sbin/qconn” to your /etc/rc.d/rc.local file to have it
launched every time the system boots, too… note that this is a
security risk, so don’t leave it running on deployed systems.–
Chris Herborth (> cherborth@qnx.com> ) - Senior Zombiologist and Tech Writer
Never send a monster to do the work of an evil scientist.
Monthly QNX newsletter - > http://www.qnx.com/news/forms/newsletter.html
Okay - I’m getting closer. The typo correction worked but I’m still getting
a “not connected” in IDE System Info.
When I Add Target, I’m inputting the IP address (172.17.17.1) and the
default port (8000). I’ve also tried selecting the “QNX Connector is on the
target machine” option but it has no affect.
-laura j.
“Joe Mammone” <hw@qnx.com> wrote in message news:dusp1v$1n7$1@inn.qnx.com…
Ok…6.2.0 didn’t have the qconfig util so you are ok there.
The second error is a typo, replace qrep with grep.
Use ‘pidin info’, rather then sin-Joe
Laura Jones wrote:
I’m running QNX 6.2.0. The target system is my own machine.qconfig = sh: qconfig: not found
pidin | qrep qconn = sh: qrep: not found
/usr/sbin/qconn = nothing - returned to the # prompt (better than an
error).
When I went to IDE System Information, my machine was still “not
connected”sin info provided Hard Drive, Host Name, and CPU info - but I’m still
unable
to determine RAM.-laura j.
“Chris Herborth” <> cherborth@qnx.com> > wrote in message
news:dupia1$nmm$> 1@inn.qnx.com> …Laura Jones wrote:
I don’t know. I don’t know what qconn is or how to check for it.
qconn is a conduit that the IDE uses for collecting data from the target
system. “pidin | grep qconn” will tell you if it’s running or not… if
not, you can launch it with “/usr/sbin/qconn”.You can add “/usr/sbin/qconn” to your /etc/rc.d/rc.local file to have it
launched every time the system boots, too… note that this is a
security risk, so don’t leave it running on deployed systems.–
Chris Herborth (> cherborth@qnx.com> ) - Senior Zombiologist and Tech Writer
Never send a monster to do the work of an evil scientist.
Monthly QNX newsletter - > http://www.qnx.com/news/forms/newsletter.html
Can you verify that you are using the proper ip address? Use ‘ifconfig
en0’ at the prompt to verify your IP address.
What if you use “localhost” as the ip in the target properties?
-Joe
Laura Jones wrote:
Okay - I’m getting closer. The typo correction worked but I’m still getting
a “not connected” in IDE System Info.When I Add Target, I’m inputting the IP address (172.17.17.1) and the
default port (8000). I’ve also tried selecting the “QNX Connector is on the
target machine” option but it has no affect.-laura j.
“Joe Mammone” <> hw@qnx.com> > wrote in message news:dusp1v$1n7$> 1@inn.qnx.com> …Ok…6.2.0 didn’t have the qconfig util so you are ok there.
The second error is a typo, replace qrep with grep.
Use ‘pidin info’, rather then sin-Joe
Laura Jones wrote:
I’m running QNX 6.2.0. The target system is my own machine.
qconfig = sh: qconfig: not found
pidin | qrep qconn = sh: qrep: not found
/usr/sbin/qconn = nothing - returned to the # prompt (better than an
error).
When I went to IDE System Information, my machine was still "not
connected"
sin info provided Hard Drive, Host Name, and CPU info - but I’m still
unable
to determine RAM.
-laura j.
“Chris Herborth” <> cherborth@qnx.com> > wrote in message
news:dupia1$nmm$> 1@inn.qnx.com> …
Laura Jones wrote:
I don’t know. I don’t know what qconn is or how to check for it.qconn is a conduit that the IDE uses for collecting data from the target
system. “pidin | grep qconn” will tell you if it’s running or not… if
not, you can launch it with “/usr/sbin/qconn”.You can add “/usr/sbin/qconn” to your /etc/rc.d/rc.local file to have it
launched every time the system boots, too… note that this is a
security risk, so don’t leave it running on deployed systems.–
Chris Herborth (> cherborth@qnx.com> ) - Senior Zombiologist and Tech Writer
Never send a monster to do the work of an evil scientist.
Monthly QNX newsletter - > http://www.qnx.com/news/forms/newsletter.html
\