[LU-3734] Posix Copytool Application Behaviour

Related — Fri, 30 Oct 2020 18:22:58 +0000

I have created this ticket as a story in order to try and capture some of the features or behaviours that would be desirable in a reference implementation of a copytool for Lustre HSM. This is intended as a way of creating a discussion around the features so that whatever is agreed can be addressed as feature enhancements.

Copytool program should have options that allow it to run either as a daemon or in the foreground.
Running in the foreground implies that telemetry such as logging and debug information will be printed to stdout and / or stderr
When run as a daemon, important event information and errors should be recorded to syslog – startup, shutdown, restart, etc.
Options should exist to log information into other files – syslog may not be appropriate for every kind of logging.
Users can request the level of detail or types of events that are reported and where to write those reports. For example, event type: archive, restore, remove
Since the volume of information could be very high, it is important to present users with options to tailor the amount of output generated so that the logs do not overwhelm the storage they are written to.
When run as a daemon, copytools should not have a controlling terminal and should run in its own session (usually achieved by double fork technique). CWD should change to the root directory and unneeded file descriptors closed, including stdin, stdout and stderr.
On startup, process should check to see if an instance is already running and exit if one is found.

Whamcloud Community JIRA

[LU-3734] Posix Copytool Application Behaviour