logtail displays lines from a standard text file and keeps track of the
offset of the end of the file so that subsequent runs only display new
lines. The file's inode is also recorded so that rotated logs can be
detected.
ok sthen
VERSION variable (pointed by sthen@), now autossh use configure.
With this fixes:
- updated option string up to OpenSSH 5.6
- when using -f, set gate_time to 0; the assumption is that
it is being used for infrastructure (i.e. in a system startup),
has been tested, and bombing out just because the remote end is
not up is not the desired behaviour.
- add AUTOSSH_MAXLIFETIME
- fix poll flags so not checking for writable when write done
- compile time TOUCH_PIDFILE option to touch pid file on connection test.
Maintainer drop the maintainership, so I take care of this now.
OK aja@, okan@.
* Use hash table to speed up hard link detection
* Added read-only option (-r)
* Use KiB instead of kiB (#3399279)
Tested on i386.
USE_GROFF is not needed.
OK jasper@, aja@
entr - a utility for running arbitrary commands when files change.
Uses kqueue(2) to avoid polling. Reads a list of files provided on
STDIN and runs the supplied command if any of them are modified.
works again.
Conflict with older versions of the client.
Make mtx-changer.conf @sample-able so we don't overwrite on update.
ok & help from sthen and aja
packages which depend on each other:
- only create the _bacula user in -main (client parts)
- only create the _bacula-sd user in -server
Change _bacula's home dir from /var/bacula to /nonexistent.
/var/bacula needs to be writable by the _bacula group and since
/usr/libexec/security actually checks that user home dirs are
group-writable, whereas /etc/security just checked if the user
home dir was a writable *file*(!), it whines every day for
every machine with bacula client installed. (This will only
affect new installations so if you're annoyed by these mails
too, just vipw and change it by hand).
ok ajacoutot@ merdely@
to use this, you also need to install the specific libdbi-drivers package
for the database you plan to use.
requested and tested by Richard Brooks, RichardBUK at FastMail.fm
checking if they're defined is wrong as -1 is a valid value to indicate
the feature is not supported. No package bumps as the code sections in
question are not being built at the moment.
from Brad
