Documentation for the collection.
| Role | Description | |
|---|---|---|
| bodsch.systemd.coredump | configure systemd-coredump | |
| bodsch.systemd.homed | configure systemd-homed | |
| bodsch.systemd.journald | configure systemd-journald | |
| bodsch.systemd.oomd | configure systemd-oomd | |
| bodsch.systemd.logind | configure systemd-logind | |
| bodsch.systemd.networkd | configure systemd-networkd | |
| bodsch.systemd.resolved | configure systemd-resolved | |
| bodsch.systemd.system | configure systemd-system | |
| bodsch.systemd.timesyncd | configure systemd-timesyncd | |
| bodsch.systemd.user | configure systemd-user |
| Name | Description |
|---|---|
| journalctl | Query the systemd journal with a very limited number of possible parameters |
| unit_file | This can be used to create a systemd unit file. The service, timer and socket types are supported. |
You can install the memsource collection with the Ansible Galaxy CLI:
#> ansible-galaxy collection install bodsch.systemdTo install directly from GitHub:
#> ansible-galaxy collection install git@github.com:bodsch/ansible-collection-systemd.gitYou can also include it in a requirements.yml file and install it with ansible-galaxy collection install -r requirements.yml, using the format:
---
collections:
- name: bodsch.systemdThe python module dependencies are not installed by ansible-galaxy. They can
be manually installed using pip:
#> pip install -r requirements.txtYou can either call modules by their Fully Qualified Collection Name (FQCN), such as bodsch.systemd.remove_ansible_backups,
or you can call modules by their short name if you list the bodsch.systemd collection in the playbook's collections keyword:
---
- name: remove older ansible backup files
bodsch.systemd.remove_ansible_backups:
path: /etc
holds: 4Please read Contribution
The master Branch is my Working Horse includes the "latest, hot shit" and can be complete broken!
If you want to use something stable, please use a Tagged Version!
- Bodo Schulz
FREE SOFTWARE, HELL YEAH!