remove sudo

Author: sashwinbalaji

docs/getting-started/cpu-profiling.md

@@ -163,8 +163,8 @@ echo -1 | sudo tee /proc/sys/kernel/perf_event_paranoid
 Assuming the example config above is saved as `/tmp/config.txtpb`, start the
 recording.
 ```bash
-sudo ./tracebox ctl start # This will start persistent background tracing services
-sudo ./tracebox -c /tmp/config.txtpb --txt -o /tmp/trace.pb
+./tracebox ctl start # This will start persistent background tracing services
+./tracebox -c /tmp/config.txtpb --txt -o /tmp/trace.pb
 ```
 
 Open the `/tmp/trace.pb` file in the [Perfetto UI](https://ui.perfetto.dev).
@@ -334,8 +334,8 @@ Assuming the example config above is saved as `/tmp/config.txtpb` (with the
 target\_cmdline option changed to a process on your machine), start the
 recording.
 ```bash
-sudo ./tracebox ctl start
-sudo ./tracebox -c /tmp/config.txtpb --txt -o /tmp/trace.pb
+./tracebox ctl start
+./tracebox -c /tmp/config.txtpb --txt -o /tmp/trace.pb
 ```
 
 Once the recording stops, open the `/tmp/trace.pb` file in the [Perfetto

docs/getting-started/ftrace.md

@@ -285,13 +285,13 @@ See the [system tracing page](/docs/getting-started/system-tracing.md) in order
 to get set up with tracebox. For this example we are going to record a trace
 from the command line using the config file we just created:
 ```bash
-sudo ./tracebox ctl start # This will start persistent background tracing services
-sudo ./tracebox -c ticker.cfg --txt -o ticker.pftrace
+./tracebox ctl start # This will start persistent background tracing services
+./tracebox -c ticker.cfg --txt -o ticker.pftrace
 ```
 
 Alternatively using autodaemonize mode:
 ```bash
-sudo ./tracebox --autodaemonize -c ticker.cfg --txt -o ticker.pftrace
+./tracebox --autodaemonize -c ticker.cfg --txt -o ticker.pftrace
 ```
 
 Note: tracebox will take care of enabling tracing and our ticker events (as we

docs/getting-started/memory-profiling.md

@@ -174,22 +174,22 @@ chmod +x tracebox heap_profile
 
 Start the tracing service
 ```bash
-sudo ./tracebox ctl start # This will start persistent background tracing services
+./tracebox ctl start # This will start persistent background tracing services
 ```
 
 Generate the heapprofd config and start the tracing session.
 ```bash
 # Replace trace_processor_shell with with the name of the process you want to
 # profile.
 ./heap_profile -n trace_processor_shell --print-config | \
-  sudo ./tracebox -c - --txt -o ~/trace_processor_memory.pftrace
+  ./tracebox -c - --txt -o ~/trace_processor_memory.pftrace
 ```
 
 Alternatively, use the autodaemonize mode (no `ctl start` required):
 
 ```bash
 ./heap_profile -n trace_processor_shell --print-config | \
-  sudo ./tracebox --autodaemonize -c - --txt -o ~/trace_processor_memory.pftrace
+  ./tracebox --autodaemonize -c - --txt -o ~/trace_processor_memory.pftrace
 ```
 
 Open another terminal (or tab), start the process you want to profile,
@@ -222,7 +222,7 @@ which you can then open with the Perfetto UI.
 
 Remember also to kill the `tracebox` services once you are done.
 ```bash
-sudo ./tracebox ctl stop
+./tracebox ctl stop
 ```
 </tabs?>
 

docs/getting-started/system-tracing.md

@@ -156,7 +156,7 @@ chmod +x tracebox
 First, start the tracing daemons in background:
 
 ```bash
-sudo ./tracebox ctl start # This will start persistent background tracing services
+./tracebox ctl start # This will start persistent background tracing services
 ```
 
 Then, to capture a trace you need to pass the config file to the downloaded `tracebox`
@@ -169,14 +169,14 @@ curl -LO https://raw.githubusercontent.com/google/perfetto/refs/heads/main/test/
 ```
 and running the following command:
 ```bash
-sudo ./tracebox -o trace_file.perfetto-trace --txt -c scheduling.cfg
+./tracebox -o trace_file.perfetto-trace --txt -c scheduling.cfg
 ```
 The scheduling information is captured using ftrace, so you may need to start
-the `tracebox` daemons with root privileges (e.g. `sudo ./tracebox ctl start`).
+the `tracebox` daemons with root privileges (e.g. `./tracebox ctl start`).
 
 If you prefer the old behavior where tracebox starts temporary daemons for the duration of the trace, you can use the `--autodaemonize` flag:
 ```bash
-sudo ./tracebox --autodaemonize -o trace_file.perfetto-trace --txt -c scheduling.cfg
+./tracebox --autodaemonize -o trace_file.perfetto-trace --txt -c scheduling.cfg
 ```
 
 </tabs?>

docs/reference/tracebox.md

@@ -29,12 +29,10 @@ multiple tracing sessions.
 **Commands:**
 
 `tracebox ctl start`
-:   Starts `traced` and `traced_probes` in the background. On Linux, running
-    as root (via `sudo`) is highly recommended to place sockets in the standard
-    `/run/perfetto/` directory.
+:   Starts `traced` and `traced_probes` in the background.
 
 `tracebox ctl stop`
-:   Stops daemons started via `ctl start` and cleans up PID files.
+:   Stops daemons started via `ctl start`.
 
 `tracebox ctl status`
 :   Checks if daemons are running, accessible, and which sockets they are using.
@@ -43,14 +41,14 @@ multiple tracing sessions.
 
 ```bash
 # Start services once (as root for full system/SDK support)
-sudo ./tracebox ctl start
+./tracebox ctl start
 
 # Record multiple traces
-sudo ./tracebox -t 10s -o trace1.pftrace sched
-sudo ./tracebox -t 10s -o trace2.pftrace sched
+./tracebox -t 10s -o trace1.pftrace sched
+./tracebox -t 10s -o trace2.pftrace sched
 
 # Stop services when finished
-sudo ./tracebox ctl stop
+./tracebox ctl stop
 ```
 
 ### 2. Autodaemonize Mode
@@ -65,7 +63,7 @@ Pass the `--autodaemonize` flag before other arguments.
 
 ```bash
 # Start daemons, record trace, stop daemons
-sudo ./tracebox --autodaemonize -t 10s -o trace.pftrace sched
+./tracebox --autodaemonize -t 10s -o trace.pftrace sched
 ```
 
 ### 3. Applet Mode
@@ -94,7 +92,7 @@ This is the preferred mode for most workflows.
 
 *   **SDK/App Tracing:** If you are tracing applications instrumented with the
     Perfetto SDK (using `track_event`), you **must** use Managed Mode (usually
-    as root). SDK applications only connect to the standard system socket paths
+    as root). SDK applications connect to the standard system socket paths
     (e.g., `/run/perfetto/` on Linux).
 *   **Repeated Tracing:** If you are recording multiple traces in succession,
     Managed Mode avoids the overhead of restarting the services for every trace.
@@ -107,6 +105,3 @@ This is the preferred mode for most workflows.
     you want to ensure no leftover processes remain after execution.
 *   **Debugging:** Quick verification of ftrace events where setting up a full
     service is unnecessary.
-*   **Limitations:** This mode uses private, randomized socket paths (e.g., in
-    `/tmp/`). Applications using the Perfetto SDK **cannot** connect to these
-    daemons, so you will not capture userspace instrumentation.