The way this is done in 6.5 is twofold (I'm going by memory here)(. First, there's the ssh opeino which does require root since it does the installation. Secondly, there's the scp option. scp simply copies the files over using a username and password that you provide and gives you instructions on how to do the install when the copy is complete (typically you would ssh to the system as yourself, sudo to root, and then run the install script).
In your case, you could edit the config file and tell it what username to use. Then scp over your public key to the target system. Then when the install script runs, it will do the copy but likely fail on the install if you're not a root user. You now see one reason (of many) why people want to stay close to current with NetBackup releases. You're having to work around limitations that were addressed in product releases last year. .../E On Tue, Aug 19, 2008 at 3:25 AM, WALLEBROEK Bart <[EMAIL PROTECTED]>wrote: > Ed, > > Thanx for the info. Creating the config file did the trick. Most likely > obvious thinking ( I wouldn't know as I am not that familiar with ssh). But > now another issue has popped up. This only works with clients on which the > root account is allowed to login directly via ssh. Do you know of any > option to add a user with the install_client_files or ssh_to client command > ? > > > Best Regards, > > Bart WALLEBROEK > Systems & Applications Management & Support Specialist > CustOPS - SDC Deployment > Tel: + 32 2 655 30 75 Mobile: + 32 478 31 61 77 > S.W.I.F.T. SCRL > > ------------------------------ > *From:* Ed Wilts [mailto:[EMAIL PROTECTED] > *Sent:* Thursday, August 07, 2008 1:30 PM > *To:* JC Cheney > *Cc:* Curtis Preston; WALLEBROEK Bart; veritas-bu@mailman.eng.auburn.edu > *Subject:* Re: [Veritas-bu] install_client_files over ssh using a > differentport > > On Thu, Aug 7, 2008 at 3:09 AM, JC Cheney <[EMAIL PROTECTED]>wrote: > >> We don't specify a port number to use - we use the default port used by >> your ssh binary. For example if you look under >> /usr/openv/netbackup/client/Solaris/solaris10 you'll find the ssh_to_client >> script. On my 6.5 test system line 129 defines SSH as an alias to the >> binary; try modifying the script so that this SSH alias includes the port >> number directive. >> >> Of course this is totally unsupported but it should "get you going". Don't >> forget that when you upgrade these mods will get overwritten... > > > Which is why I suggested earlier this week that the original poster create > ~.ssh/config instead. It's totally supported and will not get overwritten. > Modifying the Symantec scripts should always be a last resort. > > .../Ed > > >
_______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
