In regard to: Re: [Networker] Some comments on NetWorker 7.4, Stan Horwitz...:

Stan, when you say nwrecover are you referring to Networker user?

I guess so. I am referring to typing "nwrecover" on the command line on the Linux client. When I do that, I get an error as follows

125:nwrecover: unable to execute with hard links to binary /usr/bin/nwrecover
I get the same error on the NSR 7.4 server too.

That's a message I've never seen before.  I wonder if it has anything to
do with SELinux?

Try modifying /etc/sysconfig/selinux on the client, setting

        SELINUX=disabled

Then reboot the client.  You should see boot messages (or run dmesg) that
eventually say

        SELinux:  Disabled at runtime.

Try running nwrecover after you've rebooted and SELinux is disabled.  If
the problem goes away, it's because EMC's packages aren't correctly
interfacing with SELinux.

Remember to re-enable SELinux and reboot after you've done your test,
assuming you want to run with it enabled.

Tim
--
Tim Mooney                                        Tim.Mooney AT ndsu DOT edu
Information Technology Services                   (701) 231-1076 (Voice)
Room 242-J6, IACC Building                        (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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