Project

General

Profile

Actions

Bug #15498

open

dtrace -A -o should leave /etc/system alone

Added by Andy Fiddaman about 1 year ago. Updated about 1 year ago.

Status:
In Progress
Priority:
Low
Assignee:
Category:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:
Bite-size
Tags:
Gerrit CR:
External Bug:

Description

It is possible to use -o with dtrace -A so that it writes the generated DOF to an alternative file, rather than updating /kernel/drv/dtrace.conf on the running system.
However, even with this option present, dtrace will modify /etc/system. This seems wrong.

Here is the default behaviour, without -o, where dtrace updates the two system files:

% pfexec dtrace -A -s anon.d
dtrace: saved anonymous enabling in /kernel/drv/dtrace.conf
dtrace: added forceload directives to /etc/system
dtrace: run update_drv(8) or reboot to enable changes

and here is what happens if the -o option is also provided:

% pfexec dtrace -A -s anon.d -o anon.out
dtrace: saved anonymous enabling in anon.out
dtrace: added forceload directives to /etc/system            <------ still modifies /etc/system
dtrace: run update_drv(8) or reboot to enable changes

I propose that if the -o option is provided, then /etc/system is left alone, and the message regarding update_drv is also unecessary.

Actions #1

Updated by Rich Lowe about 1 year ago

Is this for an altroot kind of scenario, where a dtrace -R would be very useful?

I agree with this bug, but I'm wondering if there's more we could do for what it is you're trying to do.

Actions

Also available in: Atom PDF