https://github.com/blob42/pswatch
Execute custom commands for predefined system conditions
https://github.com/blob42/pswatch
executor monitoring process resource-control scheduler task timer
Last synced: 6 months ago
JSON representation
Execute custom commands for predefined system conditions
- Host: GitHub
- URL: https://github.com/blob42/pswatch
- Owner: blob42
- License: agpl-3.0
- Created: 2024-07-28T08:53:54.000Z (over 1 year ago)
- Default Branch: master
- Last Pushed: 2025-07-18T21:23:05.000Z (7 months ago)
- Last Synced: 2025-07-18T21:53:42.860Z (7 months ago)
- Topics: executor, monitoring, process, resource-control, scheduler, task, timer
- Language: Rust
- Homepage: https://git.blob42.xyz/blob42/pswatch
- Size: 108 KB
- Stars: 5
- Watchers: 1
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
- License: LICENSE
Awesome Lists containing this project
README
# PSWatch
Run custom commands when defined system conditions are met.
pswatch is a minimalist process monitoring and task scheduler that allows you to
watch system processes and run custom commands when specific conditions or
patterns are matched.
**Features**
- Process Matching: match running processes by substring or regex patterns in name, exe path or the entire command line.
- Define conditions and actions.
- Execute actions when conditions are met on the matched processes.
- Create multiple profiles for complex conditions and action sets
- Systemd `notify` process type integration.
## Installation
### From Crates.io
`cargo install pswatch`
### From source
```sh
git clone https://github.com/blob42/pswatch.git
cd pswatch
cargo install --path .
```
## Usage
Pswatch requires a `TOML` based configuration file. By default it uses the config file under `$XDG_CONFIG_DIR/pswatch/config.toml` or the one provided as parameter.
```sh
./pswatch -c /path/to/config.toml
```
The program will watch system processes and execute commands based on the
patterns defined in the configuration file.
## Configuration File
pswatch's behavior is configured using a TOML-formatted configuration file. The
file should contain a list of `profiles`, each containing a `matching` directive
(the process to match), an (optional) `regex` flag (set to `true` if the
pattern is a regular expression), and a list of `commands`.
Each command contains a condition (either `seen` or `not_seen` with a duration)
and an array of shell commands (`exec`) to execute when the condition is met. An
optional `run_once` flag can be set to run the command only once per process
detection.
Here's an example configuration file:
```toml
[[profiles]]
matching = { name = "foo" }
# command 1
[[profiles.commands]]
condition = {seen = "5s"}
exec = ["sh", "-c", "notify-send psw 'foo action'"]
# command 2
[[profiles.commands]]
condition = { not_seen = "60s" }
exec = ["sh", "-c", "notify-send psw 'where is foo ?'"]
run_once = true
```
## Example: Toggle Power Saving
Here is a more realistic example that toggles the CPU turbo mode or power saving when a compilation job is detected:
```toml
[[profiles]]
# matches common compilers for C,C++ and Rust
matching = { name = 'cc1.*|^cc$|gcc$|c\+\+$|c89$|c99$|cpp$|g\+\+$|rustc$', regex = true }
[[profiles.commands]]
condition = {seen = "3s"}
# command to execute when condition is met
exec = ["sh", "-c", "enable_turbo"]
# when exec_end is defined the schedule behaves like a toggle
# command is executed when exiting the condition
exec_end = ["sh", "-c", "disable_turbo"]
```
## Example: dynamic nvidia-smi power profile for compute workloads
```toml
[[profiles]]
matching = { cmdline = "llama.cpp|ollama runner|localai", regex = true}
[[profiles.commands]]
condition = {seen = "1s"}
exec = [ "sh", "-c", "sudo nvidia-smi -pl 280" ]
[[profiles.commands]]
condition = {not_seen = "30s"}
exec = [ "sh", "-c", "sudo nvidia-smi -pl 100"]
```
## Examples with Multiple Profiles
You can use multiple profiles within a single configuration file to monitor different processes and execute commands for matched conditions.
Here's an example configuration that uses two profiles:
```toml
[[profiles]]
pattern = "bar"
# matches the process name
matching = { name = "bar" }
[[profiles.commands]]
condition = {not_seen = "5s"}
exec = ["sh", "-c", "notify-send psw 'bar not seen!'"]
[[profiles]]
# matches the full executable path
matching = { exe_path = '.*baz$', regex = true}
[[profiles.commands]]
condition = {seen = "10s"}
exec = ["sh", "-c", "notify-send psw '/baz action !'"]
run_once = true # run the command only once when a match is triggered
[[profiles]]
# matches the command line
matching = { cmdline = '\-buz.*', regex = true}
[[profiles.commands]]
condition = {seen = "10s"}
exec = ["sh", "-c", "notify-send psw 'someproc -buz action !'"]
```
In this example, pswatch will watch for three processes: "bar", "baz" and "buz".
- It matches `bar` by process name (simple string).
- Matches `.*baz$` and `\-buz.*` by a regex pattern of the executable path and
command line respectively.
- When "bar" is not seen for 5 seconds, it will execute the `exec` action.
- When "baz" (a regular expression) is detected, it will execute the
corresponding `exec` after a delay of 10 seconds.
- The command for "baz" will be run only once per process detection.
## Example Scenarios
1. **Execute a command when a specific process is seen for a certain duration**
- Define a watch with the desired process name and use `{seen = "duration"}` to specify that the command should be executed when the process has been running for a specified duration (e.g., "5s").
2. **Execute a command when a specific process is not seen for a certain duration**
- Define a watch with the desired process name and use `{not_seen = "duration"}` to specify that the command should be executed when the process has been absent for a specified duration (e.g., "5s").
3. **Execute multiple commands based on different conditions**
- Define multiple watch configurations in the same TOML file and specify separate `condition` and `exec` settings for each. pswatch will monitor all configured profiles and execute their respective commands when appropriate.
## Systemd User Unit
```ini
[Unit]
Description=pswatch process watcher
[Service]
Type=notify
ExecStart=%h/.cargo/bin/pswatch
Restart=on-failure
; Use this to enable debug or trace
;Environment=RUST_LOG=debug
[Install]
WantedBy=default.target
```
## Troubleshooting
You can enable more verbose output using the `-d` flag or setting the environment variable to `debug` or `trace`.
## Contributing
Contributions are welcome ! If you'd like to contribute, please follow these steps:
1. Fork the repository on GitHub.
2. Clone your fork to your local machine: `git clone
https://github.com/your-username/pswatch.git`.
3. Create a new branch for your changes: `git checkout -b my-feature`.
4. Make your changes and commit them with descriptive messages:
`git commit -am 'Add some feature'`.
5. Push your branch: `git push origin my-feature`.
6. Submit a pull request from your GitHub fork to the main repository.
## License
pswatch is licensed under the AGPLv3 License.
See [LICENSE](LICENSE) for more details.