>Once trace points are added tracing can be used to answer all sorts of
>questions.
Yes. We've been tracing such information (and others) using DTrace/PID provider
for years, however having those more abstract probes is going to make it easier
for everyone,
especially in cases where you
On 12/3/2018 6:56 AM, Robert Milkowski wrote:
> Hi,
>
>
>
> Just a teaser:
>
>
>
> # dtrace -q -n vlserver*:::*GetEntry-done* \
>
> '{printf("%Y client: %s volname: %s rc: %s\n", walltimestamp, \
>
> args[1]->ci_remote, args[3]->volname, afs_errorstr[args[0]]);}'
>
>
>
> 2018
On Fri, 30 Nov 2018, Benjamin Kaduk wrote:
> The situation tends to be fairly customized for each site (and is not a
> terribly common operation), so I don't know of any formal documentation.
> The thread starting at
> https://lists.openafs.org/pipermail/openafs-info/2017-January/042007.html
> is
Hi,
Just a teaser:
# dtrace -q -n vlserver*:::GetEntry-done \
'{printf("%Y client: %s volname: %s rc: %s\n", walltimestamp, \
args[1]->ci_remote, args[3]->volname, afs_errorstr[args[0]]);}'
2018 Nov 19 15:55:15 client: 10.170.57.130 volname: zz.vldb.13 rc: OK
2018 Nov 19
