I've put in a DCR trying to get this changed back, in fact.  There's no
good reason for everyone who might run a backup or archive--including
DBAs, application/business users, etc.--to have write access to the file
like that.  And it runs contrary to the current climate of increasing
security.

DCRs from other users might help the process along...



_________________________________

Kathleen Hallahan
Freddie Mac
Distributed Backups
703-450-3317




   "Paul Zarnowski" <psz1 AT CORNELL DOT EDU>
   Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
   12/02/2005 04:53 PM
   Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
dsmerror.log in TSM 5.3






Ok, so TSM client development has decided that starting with TSM 5.3,
the dsmerror.log file has to be writable, or else it will fail.

Why?  What was the overwhelming reason to make this behavior change?

Unless I am missing an easy solution to this problem, this is going
to cause our users grief, and I don't see a simple solution.  I liked
it better when the client just continued to work, but didn't write to
the error log.  Now we have to explain to our users that they have to
rewrite their scripts, or they have to set environment variables, or
they have to be careful which directory they run TSM out of.  They
don't need this annoyance.  I don't see the reason for the change.

grr.

Does anyone know if MacOS X has something similar to an /etc/environment
file?

..Paul


--
Paul Zarnowski                            Ph: 607-255-4757
Manager, Storage Systems                  Fx: 607-255-8521
719 Rhodes Hall, Ithaca, NY 14853-3801    Em: psz1 AT cornell DOT edu