The commands inside of my /etc/config/sysinit.1 are not being executed at
all. How can I make the qnx execute this file when it starts?
Ed
What are the symptom? Are you sure the machine is node 1
“Edwin Mercado” <emerado@wpi.edu> wrote in message
news:Pine.OSF.4.21.0008251031480.6877-100000@reno.WPI.EDU…
The commands inside of my /etc/config/sysinit.1 are not being executed at
all. How can I make the qnx execute this file when it starts?Ed
The problem was that I had added my commands after:
if test -f /etc/config/bin/tcpip.$NODE
then
… /etc/config/bin/tcpip.$NODE
fi
if test -f /etc/config/bin/ph.$NODE
then
… /etc/config/bin/ph.$NODE
else
tinit -t /dev/con1 &
fi
After moving my program calls before these lines every is working now.
Thanks
Edwin
p.s. filename: /etc/sysinit.1
On Fri, 25 Aug 2000, Mario Charest wrote:
What are the symptom? Are you sure the machine is node 1
“Edwin Mercado” <> emerado@wpi.edu> > wrote in message
news:> Pine.OSF.4.21.0008251031480.6877-100000@reno.WPI.EDU> …
The commands inside of my /etc/config/sysinit.1 are not being executed at
all. How can I make the qnx execute this file when it starts?Ed
\
Previously, Edwin Mercado wrote in comp.os.qnx:
The commands inside of my /etc/config/sysinit.1 are not being executed at
all. How can I make the qnx execute this file when it starts?
Are you getting any error messages? Just the system just “hang”?
One thing you can try: ensure that the node is actually setup as node1. What parameters are you passing to Proc32 in your build file? The ‘-l’ option specifies the node number. If the ‘-l’ option passed to Proc32 is something other than 1, just change the sysinit.1 to sysinit.nodeNumber.
For more information on Proc32, please see the QNXOS Utilities - N to Z manual.
Ed
For more information on Proc32, please see the QNXOS Utilities - N to Z manual.
I don’t normally reply to myself on newsgroups… but I’m feeling schizophrenic…
If you don’t have the printed manuals, they are also avaiable online. The link for info on Proc32 is support.qnx.com/support/docs/qnx4/utils/p/proc.html
Ed
\
You might try putting
set -v
as the first line in your sysinit.1 file.
This will allow you to see how far things
go.
\
Mitchell Schoenbrun --------- maschoen@pobox.com
Another thing I do in all of my sysint and other shell scripts is something
like:
echo “Currently Executing $0”
this way I know the instant the system comes up what the node number is and
if I’m doing an alt-boot, etc.
Mitchell Schoenbrun <maschoen@tsoft.com> wrote in message
news:sqds7l9rt9151@corp.supernews.com…
You might try putting
set -v
as the first line in your sysinit.1 file.
This will allow you to see how far things
go.
\Mitchell Schoenbrun --------- > maschoen@pobox.com
What node is you system (set in /.boot built from /boot/build/xxx)
If you don’t want sysinit to be node specific name it [sysinit] not
[sysinit.$NODE]
Edwin Mercado <emerado@wpi.edu> wrote in message
news:Pine.OSF.4.21.0008251031480.6877-100000@reno.WPI.EDU…
The commands inside of my /etc/config/sysinit.1 are not being executed at
all. How can I make the qnx execute this file when it starts?Ed
Edwin Mercado <emerado@wpi.edu> wrote:
The commands inside of my /etc/config/sysinit.1 are not being executed at
all. How can I make the qnx execute this file when it starts?
What node do you see when you run “sin info”?
If it is node 1, then there is something of a
mystery going on. Are you pressing ESC
at boot time? How do you know that it
is not being executed?
–
Mitchell Schoenbrun --------- maschoen@pobox.com