On Tue, Dec 22, 2015 at 10:32:33AM +0100, Antoine Jacoutot wrote: > On Tue, Dec 22, 2015 at 10:12:09AM +0100, Landry Breuil wrote: > > On Tue, Dec 22, 2015 at 07:56:35AM +0100, Antoine Jacoutot wrote: > > > On Mon, Dec 21, 2015 at 10:43:01PM +0100, Landry Breuil wrote: > > > > On Mon, Dec 21, 2015 at 09:29:00AM -0800, Eric Lalonde wrote: > > > > > Hello ports@, > > > > > > > > > > databases/barman has been updated to 1.5.1. Changes include improved > > > > > support > > > > > for WAL maintenance operations and various bug fixes. > > > > > > > > > > Full Changelog can be found at: > > > > > > > > > > http://sourceforge.net/projects/pgbarman/files/1.5.1/README.txt/download > > > > > > > > > > Note barman now supports a configurable lock directory. Upstream has > > > > > set > > > > > this to /var/run/barman. After grepping through the ports tree, I > > > > > didn't see > > > > > any strong convention about lockfile locations. (things seem to be > > > > > scattered > > > > > around /var/run/, /var/spool, and /var/lock). After reading hier(7) I > > > > > still > > > > > wasn't sure where a non-mail-related lock directory should go, so I > > > > > left it > > > > > as-is. Happy to discuss. > > > > > > > > Well, if you want to use /var/run/barman you'll have to @sample like log > > > > and db subdirs it so that _barman can write to it :) > > > > > > Which makes no sense since /var/run/ content is removed at boot time. > > > > Right, then since barman is supposed to run from cron we cant really use > > an rc script creating this dir, so you'll have to find another default dir. > > Hmm but if it's just for a lock file, /var/run/ is fine, isn't it?
Sadly, nope, since barman is supposed to be run from _barman's crontab, (as shown in the pkg README) which has no write rights on /var/run - hence the possibility of a subdir owned by _barman, but since there's no rc script to create it like its done for ckit or dbus... Landry
