Made one little enhancement to the manifest for controlling the TSM Scheduler via SMF.. This is useful if you are running multiple scheduler processes on the same machine in different zones. (Which is “not supported” by IBM). Also to make TSM work in a zoned environment (where /usr is read only in the zones) you will need to remove the symlinks from /opt/tivoli/tsm/client/ba/bin/dsm.[opt|sys] to /usr/bin/dsm.[opt|sys] and make the links the other way around, by putting the actual config files in /opt/…/ba/bin/dsm.[opt|sys] and making a symlink to them from /usr/bin/dsm.[opt|sys]. This allows for per zone config’s. In my previous manifest if you stopped and restarted the dsmc scheduler in the global zone it killed the schedulers in all zones. So I have changed the pkill command to just be
This way only the zone you want it to die in will get touched…(Note, those are back tick’s around the zonename command)
Here is the manifest:
< !DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1">
<service_bundle type="manifest" name="TIVsmCba:dsmc">
<service name="application/dsmc" type="service" version="5">
<create_default_instance enabled="false"/>
<single_instance />
<dependency name="fs-local" grouping="require_all" restart_on="none" type="service">
<service_fmri value="svc:/system/filesystem/local"/>
</dependency>
<exec_method type="method" name="start" exec="/opt/tivoli/tsm/client/ba/bin/dsmc sched > /dev/null 2>&1 &" timeout_seconds="60"/>
<exec_method type="method" name="stop" exec="/usr/bin/pkill -z`zonename` dsmc" timeout_seconds="60"/>
<stability value="Unstable"/>
<template>
<common_name>
<loctext xml:lang="C">Tivoli Storage Manager Client</loctext>
</common_name>
</template>
</service>
</service_bundle>
Technorati Tags: Solaris, OpenSolaris, SMF, Tivoli