Greg - It's unusual and unhealthy, from both logical an physical
standpoints,
to mingle the error logging from all sessions - which may involve
simultaneous sessions. In such an error log, you want a clear-cut
sequence
of operations and consequences reflected.
What I would recommend is the creation of a wrapper script for dsmc,
named
the same or differently, which will put all error logs into a single,
all-writable directory, with an error log path spec which appends the
username, for uniqueness and singularity. The wrapper script would
invoke
dsmc with the -ERRORLOGname= option spec.
Richard Sims http://people.bu.edu/rbs
On Sep 22, 2004, at 12:38 PM, Greg wrote:
Hi,
I am having a little trouble getting the client error log set up
correctly for non-administrators on MacOS X servers. I have defined
ERRORLOGName in /Library/Preferences/Tivoli Storage Manager/TSM System
Preferences file. As it should this definition overrides any
environmental export of DSM_LOG by the non-administrator user. However
when the dsmerror.log is written by the TSM scheduler the mode on the
file is 644 and owned by root:wheel. So when the non-administrator user
invokes DSMC they get the infamous 'ANS0110E Unable to open error log
file '/path/to/dsmerror.log' for output" problem.
If leave the path undefined in the dsm.sys the export of DSM_LOG for
each user works correctly. But I want all system invoked TSM logs
written to the hosts central log path, and any user TSM logs written to
the path of there choice. I just can't seem to find a way to do it.
Can someone shed some light on this for me?
Thanks,
Greg
|