George Sinclair wrote:
I'd like to run a check on a client file index using nsrck.
1. Will the nsrck command work with the server stopped?
No of course not, the nsrindexd needs to be running, which means the
other daemons must also be running.
2. Must the server be stopped before running it?
No, see above.
3. Does it depend on what level you're using, assuming it's less than 7?
No.
4. What's the worst case scenario if the server is not stopped?
Err, mutually assured destruction.
Even if you know there will be no save operations running against that
client, I guess the server could still truncate the client's index
entries which it's going to do at some point every day. Would it do
that, though, if nsrck was running against that client index?
Why would it matter?
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the body of the email. Please write to networker-request
AT listserv.temple DOT edu if you have any problems with this list. You can access the
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
