Simon Sadedin

In fact, it does use inotify already for file based events, but unfortunately that presents its own issues - see #210.

Can you say a bit more exactly what you did? Did you clone the repository and build it? did you download a release (which one?). The above error might occur...

It does use file modification timestamps, although because the modification times on some file systems are quite coarse (commonly 1 second resolution or even greater) it actually stores the time...

This is an unfortunate side effect of recent changes made to use native file system events (inotify) to know when files get created / modified. You can turn off use...

Also, one aspect of this is that it registers one inotify instance per output directory. So if you are creating a huge number of directories as part of your pipeline,...

@MattSANU - I'm not entirely sure, but it is possible that Java itself falls back to a manual approach. Bpipe tries first to create a high sensitivity notification and then...

See https://github.com/ssadedin/bpipe/issues/168 for LSF implementation

The class it is looking for (bpipe.Runner) should be found in /usr/local/apps/bpipe/0.9.9.2/lib/bpipe.jar - can you check that file exists? NB: If you just cloned your install out of Github then...

@jsmedmar, do you think that it is possible your issue is related to #175? It has the effect that checks may be skipped incorrectly, which might be contributed to your...

closing as stale - bpipe docs are rehosted now on a different location with TLS/SSL.