You are right, there are some backward restrictions in tsm... Most notable, the
users stanza in dsm.sys on unix, and then every user being able the set DSM_DIR
and create his own dsm.sys the way he likes it That is btw the second way
to avoid having anything to do with the logfiles as define
"ADSM: Dist Stor Manager" skrev: -
Till: ADSM-L@VM.MARIST.EDU
Från: Steve Harris
Sänt av: "ADSM: Dist Stor Manager"
Datum: 11/22/2010 22:22
Ärende: Re: Seemingly stupid dsmadmc behavior
Hi Remco
Thanks for your suggestion, I hadn't thought of that and it does
Hi Remco
Thanks for your suggestion, I hadn't thought of that and it does work
nicely
However, the fact that it does work merely underlines my point that the
original restriction on overriding the log location with the DSM_LOG
environment variable is essentially pointless and just makes things
un
group and grant
access to group.
From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf Of Steve Harris
[st...@stevenharris.info]
Sent: Thursday, November 18, 2010 12:46 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Seemingly stupid dsmadmc behavior
How about: alias dsmadmc=dsmadmc -errorlogname=~/dsmerror.log ?
Wouldn't that do the trick?
--
Gr., Remco
On 17 nov. 2010, at 22:46, Steve Harris wrote:
> Time for a bit of a rant.
>
>
> I have a new 5.5 server on Solaris. For reasons that I understand even if
> it does make my life more di
Time for a bit of a rant.
I have a new 5.5 server on Solaris. For reasons that I understand even if
it does make my life more difficult, I am not permitted to have root access
on this box, and the Solaris guys have determined that they want the TSM
client log files on /var/adm/log/tsm
So dsm.sy
