Thank you for the response. We only have a problem when we have 2 /dev/ser
ports started in rapid succession, and start a /dev/con with a third tinit
at about the time that the dev/ser tinit’s are using resources.
The problem only occurs with low memory, (1.7 meg) and about 10% - 100% of
the time, depending on minor time delays between the three tinits. We get a
variety of errors, such as:
various files followed by “no such file or directory”
“Error: System File I/O error (jam.lib)”,
“menu: not found”,
“/usr/spec/db/err.os: cannot open (no such file or directory)”,
yet these files always exist, and are not being created or destroyed.
Manually stepping through the initialization (allowing each process to
complete) eliminates the problem, which seems to point to some resource
being in short supply. Adding “sleeps” does a similar “work around”.
Our initial thinking is the system is running out of some resource, and when
additional disk access is tried, it cannot execute, therefore fails, and the
failure is often interpreted as “not found”.
The $PATH shows the correct path. We do not know for sure “tinit” is the
problem, but it appears to be involved, and the documentation comments
concerned us. Just running /dev/ser1 without “tinit”, used as an I.O port,
and 2 separate "tinit"s on /dev/ser2 and /dev/con1 appear to work fine for
us also.
“osinfo” shows no resource below 50%, except memory at about 5%.
andy <andy@microstep-hdo.sk> wrote in message
news:39D9A097.BA93CC51@microstep-hdo.sk…
We use two tinit-s at once, one for login on consoles as usual, one for
remote login on /dev/ser1. It operates without any problems.
Ross Libby wrote:
In the older manual, QNX Utilities Reference N-Z(1995) it states
“Only one invocation of tinit can be run per node”. We take this
to mean that if a login command is to be invoked on serial ports
/dev/ser1 and /dev/ser2 they should be invoked by the same
single tinit command, using extensive options, or a file
containing the options with the -f option.
In the new manual (Aug 1998), no such statement is made. But
it says “tinit may become very long”, inplying just one tinit
command should be used.
Do you really mean, that once “tinit” has been started,
that it must be slayed before starting it again? If so,
why does it not test for that when it starts?
Ross Libby