syscall. Recording requires privilege; every inspection, analysis, verification, and export command is read-only and unprivileged.
Usage
Global options
The default database is
~/.local/share/syscall/syscall.db.
Commands
info
record
The
-- separator is required. The target is executed directly, not through a shell.
Record exit codes
sessions
Sessions are listed newest first with status, scope, time, event count, and duration.
inspect
events
Valid event types:
processes
tree
timeline
Ordering is
timestamp_ns ASC, monotonic_ns ASC, id ASC.
files
openat arguments and may be relative or truncated. See Investigate a session.
connections
0. It does not prove an established session, TCP or UDP, reachability, or data transfer.
stats
Reports duration, process-instance count, event counts, collection and loss counters, unresolved identity count when available, and session termination state.
analyze
Severity:
informational (or info), low, medium, high, critical.
Confidence: low, medium, high.
Rule IDs:
--output truncates an existing file and sets mode 0600. It does not imply --json; the text or JSON format follows the other flags.
verify
export
The destination directory must exist. The package is written atomically with mode
0600. Existing files are not replaced without --force.
verify-export
Time inputs
--from and --to accept:
- Integer nanoseconds since the Unix epoch.
- RFC3339 UTC timestamps ending in
Zorz, such as2026-11-10T12:34:56Zor2026-11-10T12:34:56.123456789Z.
--from must be less than or equal to --to.
Output and errors
- Text output is intended for people and escapes control characters in untrusted fields.
- JSON output is valid UTF-8 and preserves nulls for unavailable values.
- Diagnostics go to stderr; data goes to stdout.
- Input, schema, and read failures return non-zero and do not modify evidence.
- Read-only commands never migrate or repair a database.