tsm_trace
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| tsm_trace [2012/04/18 09:43] – michael | tsm_trace [2021/04/24 07:40] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Trace ====== | ====== Trace ====== | ||
| + | |||
| + | kctune atdd_trace_level=1 | ||
| + | kctune atdd_direct_trace=1 0 default | ||
| + | |||
| + | |||
| + | |||
| + | label libvol TS3500-03-3592JB3 search=bulk labelsource=barcode checkin=scr overwrite=yes waitt=0 | ||
| Line 19: | Line 26: | ||
| PVR MMS ADDMSG | PVR MMS ADDMSG | ||
| + | | ||
| + | ===== Script zum Beenden eines Traces nach Auftreten einer Meldung im Log ===== | ||
| + | | ||
| + | Here is a sample script, COND_END_TRACE, | ||
| + | Storage Manager server and storageagent TEST-STA after message ANR8779E | ||
| + | has been written into the activitylog, | ||
| + | administrative schedule to run the script:: | ||
| + | | ||
| + | And for those who want to cut and paste the " | ||
| + | here we go: | ||
| + | Please be aware that each line starts with either DEFINE or UPDATE SCRIPT, perhaps your browser is fornatting it differently - so please check before running the script :-) | ||
| + | |||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
tsm_trace.1334742199.txt.gz · Last modified: 2021/04/24 07:38 (external edit)
