Hi,
I’ve been working with chkfsys on my system for a while. Lately, however, I
came across a minor problem with it. I have set the options to be quiet,
fix problems automatically, and not to ask the user for input. The problem
came up when it actually DID ask for input from the user, and it took a few
minutes to figure out why the system wouldn’t load properly. It isn’t the
biggest problem, but I wanted to know what cases might force chkfsys to ask
for input, overriding the request to not ask the user. If this is normal, I
might just write an app to pass Enter commands to chkfsys when it runs as a
work around.
Thanks!
Ron
Quiet mode only suppress the output going to the screen, but it will still
ask questions when required. There is a prompt suppression mode ( -P ) that will
do what you want. With the prompt suppression mode it will fix all minor errors,
but if it encounters a major error it will exit with an appropriate exit code.
Jason
Ron Cococcia <ron@mapson.com> wrote:
: Hi,
: I’ve been working with chkfsys on my system for a while. Lately, however, I
: came across a minor problem with it. I have set the options to be quiet,
: fix problems automatically, and not to ask the user for input. The problem
: came up when it actually DID ask for input from the user, and it took a few
: minutes to figure out why the system wouldn’t load properly. It isn’t the
: biggest problem, but I wanted to know what cases might force chkfsys to ask
: for input, overriding the request to not ask the user. If this is normal, I
: might just write an app to pass Enter commands to chkfsys when it runs as a
: work around.
: Thanks!
: Ron
I think QSSL would be interested if you document the
circumstances. It may be that the program came upon
a situation that the programmer was not willing to
handle automatically.
Previously, Ron Cococcia wrote in qdn.public.qnx4:
Hi,
I’ve been working with chkfsys on my system for a while. Lately, however, I
came across a minor problem with it. I have set the options to be quiet,
fix problems automatically, and not to ask the user for input. The problem
came up when it actually DID ask for input from the user, and it took a few
minutes to figure out why the system wouldn’t load properly. It isn’t the
biggest problem, but I wanted to know what cases might force chkfsys to ask
for input, overriding the request to not ask the user. If this is normal, I
might just write an app to pass Enter commands to chkfsys when it runs as a
work around.
Thanks!
Ron
\
–
Mitchell Schoenbrun --------- maschoen@pobox.com
Ok, I got some more information about this.
The error that it reports is something along the lines of “Lost Link, cannot
fix (paused)” where it waits for input. The options say to not ask for user
input at all.
Now this makes me a little worried, what does Lost Link mean? And if it
cannot be fixed, how can I possibly rebuild the data to work again to avoid
this error? Third, what could cause a link to be lost (I would like to know
so I might avoid this again later)?
Any help is appreciated (especially from QSSL).
TIA,
Ron
“Ron Cococcia” <ron@mapson.com> wrote in message
news:8vutrd$55t$1@inn.qnx.com…
Hi,
I’ve been working with chkfsys on my system for a while. Lately, however,
I
came across a minor problem with it. I have set the options to be quiet,
fix problems automatically, and not to ask the user for input. The
problem
came up when it actually DID ask for input from the user, and it took a
few
minutes to figure out why the system wouldn’t load properly. It isn’t the
biggest problem, but I wanted to know what cases might force chkfsys to
ask
for input, overriding the request to not ask the user. If this is normal,
I
might just write an app to pass Enter commands to chkfsys when it runs as
a
work around.
Thanks!
Ron
Jason,
I posted some more information about this problem in this thread (and pasted
it to the end of this message). Any info is appreciated as to possible ways
to fix it.
TIA
Ron
– Pasted from follow up message –
Ok, I got some more information about this.
The error that it reports is something along the lines of “Lost Link, cannot
fix (paused)” where it waits for input. The options say to not ask for user
input at all.
Now this makes me a little worried, what does Lost Link mean? And if it
cannot be fixed, how can I possibly rebuild the data to work again to avoid
this error? Third, what could cause a link to be lost (I would like to know
so I might avoid this again later)?
“Jason Clarke” <jclarke@qnx.com> wrote in message
news:900ddq$jog$1@nntp.qnx.com…
Quiet mode only suppress the output going to the screen, but it will still
ask questions when required. There is a prompt suppression mode ( -P )
that will
do what you want. With the prompt suppression mode it will fix all minor
errors,
but if it encounters a major error it will exit with an appropriate exit
code.
Jason
Ron Cococcia <> ron@mapson.com> > wrote:
: Hi,
: I’ve been working with chkfsys on my system for a while. Lately,
however, I
: came across a minor problem with it. I have set the options to be
quiet,
: fix problems automatically, and not to ask the user for input. The
problem
: came up when it actually DID ask for input from the user, and it took a
few
: minutes to figure out why the system wouldn’t load properly. It isn’t
the
: biggest problem, but I wanted to know what cases might force chkfsys to
ask
: for input, overriding the request to not ask the user. If this is
normal, I
: might just write an app to pass Enter commands to chkfsys when it runs
as a
: work around.
: Thanks!
: Ron