nandi/atop-analyze · 167e823

⑂ 167e823

Use run0 rather than sudo in setup commands

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

nandithebull committed 2026-09-21T18:49:32-07:00 Browse files

167e823 parent: 098793c

modified README.md +4 -4 Viewed

@@ -56,8 +56,8 @@ average short spikes away.
56	56
57	57	```sh
58	58	# Arch
59		-sudo pacman -S atop
60		-sudo systemctl enable --now atop.service atopacct.service atop-rotate.timer
	59	+run0 pacman -S atop
	60	+run0 systemctl enable --now atop.service atopacct.service atop-rotate.timer
61	61	```
62	62
63	63	`atopacct.service` adds process accounting, so processes that exited during an
@@ -68,8 +68,8 @@ The default sample interval is 600s, which averages a two-minute spike into
68	68	near-invisibility. For chasing spikes, drop it to 60s:
69	69
70	70	```sh
71		-sudo sed -i 's/^LOGINTERVAL=.*/LOGINTERVAL=60/' /etc/default/atop
72		-sudo systemctl restart atop.service
	71	+run0 sed -i 's/^LOGINTERVAL=.*/LOGINTERVAL=60/' /etc/default/atop
	72	+run0 systemctl restart atop.service
73	73	```
74	74
75	75	That is ~10x the samples; `LOGGENERATIONS` in the same file controls retention

  ```sh
  # Arch
--sudo pacman -S atop
++run0 pacman -S atop
--sudo systemctl enable --now atop.service atopacct.service atop-rotate.timer
++run0 systemctl enable --now atop.service atopacct.service atop-rotate.timer
  ```
  `atopacct.service` adds process accounting, so processes that exited during an
  near-invisibility. For chasing spikes, drop it to 60s:
  ```sh
--sudo sed -i 's/^LOGINTERVAL=.*/LOGINTERVAL=60/' /etc/default/atop
++run0 sed -i 's/^LOGINTERVAL=.*/LOGINTERVAL=60/' /etc/default/atop
--sudo systemctl restart atop.service
++run0 systemctl restart atop.service
  ```
  That is ~10x the samples; `LOGGENERATIONS` in the same file controls retention