Should work if environ. Variable is set for networker path. Or else default
is c:\program files\legato\nsr\bin
Sent from my Galaxy S...
On Nov 30, 2011 12:58 PM, "Bell Jr, Robert" <BellR AT uhd DOT edu> wrote:
> What is the path for the command
>
>
>
>
>
> Robert L. Bell, Jr.
> Data Center Specialist 1
> Information Technology
> University of Houston Downtown
> 713-221-8224
> bellr AT uhd DOT edu
>
>
>
>
> On Nov 30, 2011, at 12:21 AM, "akshay bhumkar" <akshay.bhumkar AT GMAIL DOT
> COM>
> wrote:
>
> Run the following command on Networker server:
>>
>> nsraddadmin -u root AT nmchost.domain DOT tld
>>
>> Thanks & Regards
>>
>> Akshay Bhumkar
>> +91-9342420444
>> *@k$h@y*
>>
>>
>>
>> On Tue, Nov 29, 2011 at 8:23 PM, Eugene Vilensky <evilensky AT gmail DOT com
>> >wrote:
>>
>> So I moved the NMC server from the backup server itself to a new host,
>>> and started using the local console authentication "administrator"
>>> account to log into the console. I set the console service to run as
>>> nobody/nobody (the default in the nmc_config script).
>>>
>>> I could monitor the backup server just fine but trying to change
>>> configuration options, received an error which paraphrased said
>>> something like
>>>
>>> "User 'root' on host 'nmchost.domain.tld' not authorized for privilege
>>> Configure NetWorker"
>>>
>>> On the backup host using nsraddadmin and verified in nsradmin:
>>> "user=root,host=nmchost.**domain.tld" was in NSR usergroup
>>> administrators.
>>>
>>> same error: "User 'root' on host 'nmchost.domain.tld' not authorized
>>> for privilege Configure NetWorker"
>>>
>>> Eventually i set "user=administrator,host=**nmchost.domain.tld" using
>>> nsraddadmin, which resolved the error.
>>>
>>> Is the error message about 'root' user, while the resolution was to
>>> add 'administrator', a bug or a feature?
>>>
>>> Thanks!
>>> -Eugene
>>>
>>> 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@listserv.**temple.edu<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<http://listserv.temple.edu/archives/networker.html>or
>>> via RSS at
>>> http://listserv.temple.edu/**cgi-bin/wa?RSS&L=NETWORKER<http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER>
>>>
>>>
>> 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@listserv.**temple.edu<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<http://listserv.temple.edu/archives/networker.html>or
>> via RSS at
>> http://listserv.temple.edu/**cgi-bin/wa?RSS&L=NETWORKER<http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER>
>>
>
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
|
