DSS - dyadic snapshot scheduler https://git.tue.mpg.de/cgit/dss/atom?h=master 2025-02-01T19:11:59Z 2025-02-01T19:11:59Z Andre Noll maan@tuebingen.mpg.de 2024-10-22T18:01:10Z urn:sha1:5770e00c6e59528762be20610af6d8bd24d6872f The doxygen comments actually make the source code harder to read, because they tend to document the obvious. Besides, they are not used uniformly accross the code base anyway. 2017-11-19T01:53:25Z Andre Noll maan@tuebingen.mpg.de 2017-11-06T00:12:41Z urn:sha1:1f5ecfacc341f893d73caa0a613d553af33a6cc9 This gets rid of existing copyright templates in favor of just the one-liner SPDX (Software Package Data Exchange) notice. All files are licensed under the GPL-2.0, so the same tag is added to each file. No copyright is changed by this commit. Several files (mostly the very short ones) did not contain a license text so far. By default all files without license information are under the default license of this package, which is GPL version 2. This commit adds the missing SPDX line so that now all files except dss.css, index.html.in, INSTALL, NEWS and README have it. We also remove author and copyright year, since the author is the same everywhere, and the year hasn't been updated any more since at least six years. Accurate information is available from the git log. The COPYING file can also be removed because the license text at https://spdx.org/licenses/GPL-2.0.html is immutable. 2017-07-13T20:54:03Z Andre Noll maan@tuebingen.mpg.de 2016-06-16T21:21:08Z urn:sha1:6c63f45a9068107cfd80aa181134574dd9373c0b In daemon mode, we must acquire the semaphore lock in the child process because the child does not inherit semaphore adjustments. Currently the parent exits successfully after the fork, so the command appears to succeed even if the child dies immediately because it was unable to acquire the lock because another dss process is holding the lock. This commit introduces a mechanism which enables the parent to tell whether the child completed its setup successfully. We create a pipe prior to calling fork(2), and let the child write to one end of the pipe after setup is complete and just before it enters the main select loop. The parent reads from the other end of the pipe and exits once the read(2) call returns. If the child dies early, read(2) returns zero, indicating failure. 2008-03-16T16:49:38Z Andre Noll maan@systemlinux.org 2008-03-16T16:49:38Z urn:sha1:e4c216f105a5f8d2ce96505685395ea7d7c08dbe