Kai Krakow

@Zygo wrote: > The csum tree stores checksums of data after it has been compressed, so it will never match duplicate data that is uncompressed, compressed with a different compression...

If it keeps backward compatibility, I like this. :-)

I'd vote for testing the backwards compatibility and if it works fine, start announcing deprecation of the old format during the next release cycle. We can then just drop support...

If you run `bees` directly without the `beesd` wrapper, it already does that. The core daemon doesn't fork into daemon mode. But it won't exit when idle, that's not implemented...

@Zygo So I'd imagine something like starting bees with a `--one-shot` option, it determines the current transid of the filesystem, and crawls the backlog until this transid. Is that your...

@Zygo Well, I used `one-shot` because it's what's used already in systemd (`Type=oneshot`) and Gentoo's package manager (`emerge --oneshot`). Probably it's used by other software, too. But as I just...

> (well, that would work if bees handled `SIGALRM` the same way as `SIGTERM`) Actually I don't read this as "walltime doesn't need bees to implement" ;-)

Yes, I think the job manager (whatever it is, cron/systemd/...) should provide infrastructure to signal the process to quit after some time. But we should document an example for this...

Yeah, I think that's mostly it except: * document an example @dim-geo Would you agree? It probably also closes some other requests in the github issues list.

@dim-geo I think "doesn't care about new subvols..." doesn't mean it ignores it. It just means it doesn't matter whether new transid was created by any of those items: Bees...