Skip to content

RTFM · Tools

Permissions, processes and logs in practice

Beyond definitions: how permissions, processes and logging interlock during real diagnostics, and the handful of idioms covering most situations.

Saphira Linux dragon mascot

Permission triage

Diagnose denials factually
id                                    # whoami effectively
namei -l /path/to/stuck/file           # per-component perms
stat file                              # full metadata

Fix ownership before modes when a copy operation imported the wrong user; guessing chmod masks the real fault.

Process inspection ladder

Process and resource interrogation
ps aux | grep -v grep | grep nginx
pgrep -af nginx

vmstat 1 5                             # sampled pressure
free -m                                # memory
uptime                                 # load context

kill -9 as opening move skips the daemon's chance to flush state politely. SIGTERM first; escalate only if genuine unresponsiveness is proven after patience.

Logs as investigation material

Identify the active log sink, then master fewer tools deeply.

Log surgery
tail -f /var/log/messages             # follow live
less +F critical.log                   # forward-scrolling viewer
zgrep ERROR rotated.log.gz             # search compressed history

Establish rotation habits deliberately via logrotate configuration matched to retention norms and disk capacity, checked quarterly. Unbounded growth equals scheduled outage.

Cross-cutting example

Layers converge
# Diagnose HTTP service acting strange:
pgrep -af haproxy
tail -n100 /var/log/haproxy.log
ss -tlnp | grep -E ':443|:80'
namei -l /etc/haproxy/haproxy.cfg      # cert/config readable?

Prove it works: unified diagnostic fluency

arbitrary misbehaving service gets examined along identity→process→resource→log axes without handbook references.

Did we miss something?

If this page left something unanswered, found an error, or there is another subject you would like documented, tell us. Saphira’s documentation grows from real problems people need to solve.

Send feedback or request a new section →

Prefer not to do it yourself?

Everything needed to do the work yourself is documented here and remains free — we charge for human time, not for withholding knowledge. Sometimes the missing resource is simply time. The same people who build Saphira can provide paid professional help with implementation, migration, troubleshooting and administration.

Ask about professional support →