On Oct 7, 2005, at 15:15:50, Derrick J Brashear wrote:
On Fri, 7 Oct 2005, Kyle Moffett wrote:
I nuked it, and now the module loads fine, but due to a defect in
my startup script I managed to start afsd twice without a /afs
directory. Now I'm in this interesting situation:
That situation is called "boned"
Indeed it is. I tried to reboot only to have it hang completely and
require a hard poweroff. It's back up and running now, and my
startup script is fixed properly to prevent that from happening
again. Theoretically it would be nice to get that bug fixed, but
I've got bigger bugs in my sights at the moment :-D.
I've discovered that all the OpenAFS commands return "Invalid
Argument", which leads me to suspect that somehow the syscall isn't
being properly registered, but I really have no clue where to look to
try to fix this. Do you have any advice for me? Thanks!
Cheers,
Kyle Moffett
--
There are two ways of constructing a software design. One way is to
make it so simple that there are obviously no deficiencies. And the
other way is to make it so complicated that there are no obvious
deficiencies. The first method is far more difficult.
-- C.A.R. Hoare
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
