From: labelles@mscd.edu
Date: Wed Mar 24 2004 - 16:05:36 EST
Hello,
I posted the following question/issue:
####################################################################
I came across a strange error/issue on a machine right after I completed an upgrade TRU64 V5.1A to V5.1B.
It shows itself if I do the following commands in single-user mode:
# /sbin/bcheckrc
# update
Then I get an error message that comes back as follows:
fuser: no such file or directory
##################################################################
The answer came from "Dr. Thomas Blinn" of HP
it somehow has to do with the PATH in single-user mode.
If I do /sbin/update
everythings okay.
Dr. Tom's answer follows:
##################################################################
This may be a silly question, but where is "update" in your
path as "single user root"? That is, what exactly are you
running when you type that command that way? If wind up in
some script that tries to run "fuser" from some place that
doesn't exist (or if "fuser" isn't in the path that's used
by the script), then you would get a message like that..
I'd want to use the explicit path /sbin/update and as far as
I can tell from looking at a V5.1A system, that's a binary
that has no references to fuser.
###################################################################
Steve
labelles@mscd.edu
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:55 EDT