DSS - dyadic snapshot scheduler https://git.tue.mpg.de/cgit/dss/atom?h=next 2024-04-27T23:26:57Z 2024-04-27T23:26:57Z Andre Noll maan@tuebingen.mpg.de 2024-04-27T23:26:57Z urn:sha1:ffc8c4a28f52cfb0e617ec3c6f3958cd994e13b6 * master: Support local make files. 2024-04-25T13:38:23Z Andre Noll maan@tuebingen.mpg.de 2024-04-25T13:38:23Z urn:sha1:73e0fd24ed41db7882948ee4d7ff63119cf5a67d These additional targets are handy for site-local targets such as installing the web files or deploying the executable and the man page on a remote server. 2024-01-29T17:27:01Z Andre Noll maan@tuebingen.mpg.de 2024-01-29T17:27:01Z urn:sha1:1b576a8fa111f2001350a18635583f020c3f07c4 * master: Fix --config-file for relative paths. 2023-11-07T14:11:55Z Andre Noll maan@tuebingen.mpg.de 2023-09-19T14:31:49Z urn:sha1:cac14c7d96355a9ca02f69627f01ddebe699afcc The dss lock works by first turning the given config file path argument into a canonical absolute path using dss_realpath(), then hashing this absolute path to obtain a key ID for semget(2). If the given path is relative, we have to compute the ID before changing to the destination directory because dss_realpath() needs to call stat(2) to detect symlinks, and this system call will fail if the current working directory has changed. This is currently not the case as we change to the destination directory early in check_config(). If dss_realpath() fails, we silently use the unmodified path argument for hashing to deal with the case that the default config does not exist. As a result, if relative paths are given, the key ID depends on whether or not change_to_dest_dir() was called. This is the case for the run subcommanmd, but not for the kill subcommand. Thus the kill subcommand does not work as expected if a relative path is given. Fix this by grabbing the lock before changing the working directory in all cases. 2023-09-19T14:46:14Z Andre Noll maan@tuebingen.mpg.de 2023-09-19T14:46:14Z urn:sha1:9c50bddaf7c66176d58094414e21fd469756c156 * master: Avoid duplicate error message. dss-1.0.1. 2020-05-17T15:08:33Z Andre Noll maan@tuebingen.mpg.de 2020-05-17T15:08:33Z urn:sha1:bf0f03c00f6de518d01b6cb1e94c1d447e5cd3b1 If parse_config_file() encounters an error, it logs the error *and* returns the error code, which causes the error message to be logged again. Fix this by removing the log statement from parse_config_file(). 2019-11-08T13:24:27Z Andre Noll maan@tuebingen.mpg.de 2019-11-08T13:24:27Z urn:sha1:53920f69b9988918e3be610e432e619c996e3e99 2019-11-07T11:31:36Z Andre Noll maan@tuebingen.mpg.de 2019-11-07T11:31:36Z urn:sha1:d6e687e0d103d43db601d3ed6744316ee8bf3277 * master: 2019-11-07T11:31:02Z Andre Noll maan@tuebingen.mpg.de 2019-11-07T11:31:02Z urn:sha1:766ebea19c1618ddab85a4fc6af2a5bf53a9ec38 A couple of cleanups and unifications for the snapshot pruning code, which is executed by the prune and run subcommands. With the patches applied, both subcommands behave identically, i.e. they consider the same set of snapshots as candidates for pruning. Also the prune command gained the new --disk-space option to force it to act as if disk space was high or low. Cooking for six weeks. * refs/heads/t/prune: Introduce prune --disk-space. Revamp com_prune(). Factor out find_removable_snapshot(). prune Simplify rm exit code logic. find_oldest_removable_snapshot(): Improve log message. prune: Print a message if there is nothing to prune. get_snapshot_list(): Add comment about sorting. prune: Fail gracefully if pre-rm hook fails. 2019-10-30T09:58:12Z Andre Noll maan@tuebingen.mpg.de 2019-10-30T09:58:12Z urn:sha1:a49a95efca7e3b22c1b06b38319fdfbeea8c7fe2 Cooking for about a month. The web page has been updated today to use the new logo. * refs/heads/t/svg-logo: Redo the logo as svg.