mirror of
https://github.com/cupcakearmy/autorestic.git
synced 2024-12-23 00:36:25 +00:00
59b2393127
This is more consistent with the `lockfile` config option
850 B
850 B
Lockfile
Under the hood, autorestic
uses a lockfile to ensure that only one instance is running and to keep track of when cronjobs were last run.
By default, the lockfile is stored next to your configuration file as .autorestic.lock.yml
. In other words, if your config file is located at /some/path/.autorestic.yml
, then the lockfile will be located at /some/path/.autorestic.lock.yml
.
Customization
The path to the lockfile can be customized if need be. This can be done is a few ways:
- Using the
--lockfile ...
command line flag - Setting
lockfile: ...
in the configuration file
Note that autorestic
will check for a customized lockfile path in the order listed above. This means that if you specify a lockfile path in multiple places, the method that's higher in the list will win.