Re: command-line equivalents of SAM functionality
From: Tapani Tarvainen (gn20040226T184928_at_tt.oma.it.jyu.fi)
Date: 02/26/04
- Previous message: Doug O'Leary: "Re: command-line equivalents of SAM functionality"
- In reply to: Wladimir Mutel: "Re: command-line equivalents of SAM functionality"
- Next in thread: Wladimir Mutel: "Re: command-line equivalents of SAM functionality"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 26 Feb 2004 18:57:37 +0200
Wladimir Mutel <mwg@fluffy.isd.dp.ua> writes:
> 2004-02-26, Tapani Tarvainen <gn20040226T153506@tt.oma.it.jyu.fi> ÐÉÛÅÔ:
> > Corné Beerse <I.Dont@want.your.spam> writes:
> >
> >> you can always peek into sam: run a `ps` to see which commands `sam` fires.
> >
> > ... or take a look at /var/sam/log/samlog after using it.
>
> It just writes :
>
> Getting the size of the disk at 8/4.8.0.
>
> Does not say what program it runs.
> May be even calls a library function ?
Look a bit earlier in the file. I find lines like this (among others):
Retrieving peripheral device configurations for device class \"DISK\".
Executing the following command:\C/usr/sam/lbin/ioparser.sh DISK\C
If you look inside ioparser.sh you'll see it uses ioscan (either
runs it when called or uses previously cached ioscan output -
samlog will even indicate which).
-- Tapani Tarvainen
- Previous message: Doug O'Leary: "Re: command-line equivalents of SAM functionality"
- In reply to: Wladimir Mutel: "Re: command-line equivalents of SAM functionality"
- Next in thread: Wladimir Mutel: "Re: command-line equivalents of SAM functionality"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]