~lukeshu/systemd - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2015-03-16	fsckd: check if plymouth is running before attempting connection	Didier Roche

2015-03-16	fsckd: Don't use strjoina on gettext() call	Didier Roche

2015-03-10	fsckd: clean up log messages	Didier Roche
	Avoid double logs printing. Not that we don't return manager_update_global_progress() to the handler callback as if the console or plymouth isn't available momentarily, we still desire to handle future fd progress events if those are available again (like cancellation, reports…)
2015-03-10	fsckd: Reduce the SAK window when writing to console	Didier Roche
	We don't want to keep /dev/console open all the time, but only open it when needed, to avoid interfering with SAK.
2015-03-09	fsck: use _cleanup_close_pair_ where appropriate	Lennart Poettering

2015-03-09	fsckd: make sure we free the connection event source before we close the ↵	Lennart Poettering
	connection fd
2015-03-09	fsckd: don't allow unbounded numbers of clients	Lennart Poettering

2015-03-09	fsckd: free client event source before we close its fd	Lennart Poettering

2015-03-09	fsck: rename functions to reflect some object orientation	Lennart Poettering
	Let's clean up the function naming scheme and put the object they operate on first in the name, the way OO programming usually does it. Also, let's make sure can properly destroy half-initialized Manager objects.
2015-03-09	fsck: don't read invalid data	Lennart Poettering

2015-03-09	fsckd: internaly check if a client already was cancelled	Lennart Poettering

2015-03-09	fsck: simplify client destruction logic	Lennart Poettering

2015-03-09	fsckd: rework plymouth connection management	Lennart Poettering
	- the even source should not be freed before the fd for it is closed - read() returns an ssize_t and we need to handle it as such - properly handle errors from read() - reuse on_plymouth_disconnect() whenever we disconnect from plymouth, and rename it plymouth_disconnect hence()
2015-03-09	fscd: fix error handling	Lennart Poettering

2015-03-09	fsck: no need for a temporary variable	Lennart Poettering

2015-03-09	fsckd: fix error handling when sending cancel request to fsck client	Lennart Poettering

2015-03-09	fsck: unify exit path for connect_plymouth()	Lennart Poettering

2015-03-09	fsck: use only a single exit code ternary operator	Lennart Poettering

2015-03-09	fsck: simplification	Lennart Poettering

2015-03-09	fsckd: the error code is actually returned in 'fd'	Lennart Poettering
	Also, we don't use {} for single-line if-blocks.
2015-03-09	fsckd: simplify code a bit	Lennart Poettering

2015-03-09	fsckd: make use of safe_close()'s return value	Lennart Poettering

2015-02-18	Translate fsckd messages for plymouth	Didier Roche
	For plymouth themes not supporting i18n (like .script), send translated messages to display to user, which is equivalent to the sent machine readable data.
2015-02-18	Connect to plymouth and support cancellation of in progress fsck	Didier Roche
	Try to connect and send to plymouth (if running) some checked report progress, using direct plymouth protocole. Update message is the following: fsckd:<num_devices>:<progress>:<string> * num_devices corresponds to the current number of devices being checked (int) * progress corresponds to the current minimum percentage of all devices being checked (float, from 0 to 100) * string is a translated message ready to be displayed by the plymouth theme displaying the information above. It can be overriden by plymouth themes supporting i18n. Grab in fsckd plymouth watch key Control+C, and propagate this cancel request to systemd-fsck which will terminate fsck. Send a message to signal to user what key we are grabbing for fsck cancel. Message is: fsckd-cancel-msg:<string> Where string is a translated string ready to be displayed by the plymouth theme indicating that Control+C can be used to cancel current checks. It can be overriden (matching only fsckd-cancel-msg prefix) for themes supporting i18n.
2015-02-18	systemd-fsck: always connect to systemd-fsckd	Didier Roche
	Remove the plymouth running or show-status checks from systemd-fsck. Instead, always connect to systemd-fsckd socket, and let this one decide if we display progress or not.
2015-02-18	fsckd daemon for inter-fsckd communication	Didier Roche
	Add systemd-fsckd multiplexer which accepts multiple systemd-fsck instances to connect to it and sends progress report. systemd-fsckd then computes and writes to /dev/console the number of devices currently being checked and the minimum fsck progress. This will be used for interactive progress report and cancelling in plymouth. systemd-fsckd stops on idle when no systemd-fsck is connected. Make the necessary changes to systemd-fsck to connect to the systemd-fsckd socket.