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

Age	Commit message (Collapse)	Author
2013-12-13	event: be more conservative when returning errors from event handler callbacks	Lennart Poettering
	We really should return errors from event handlers if we have a continous problem and don't know any other solution.
2013-12-11	event: hook up sd-event with the service watchdog logic	Lennart Poettering
	Adds a new call sd_event_set_watchdog() that can be used to hook up the event loop with the watchdog supervision logic of systemd. If enabled and $WATCHDOG_USEC is set the event loop will ping the invoking systemd daemon right after coming back from epoll_wait() but not more often than $WATCHDOG_USEC/4. The epoll_wait() will sleep no longer than $WATCHDOG_USEC/4*3, to make sure the service manager is called in time. This means that setting WatchdogSec= in a .service file and calling sd_event_set_watchdog() in your daemon is enough to hook it up with the watchdog logic.
2013-11-27	Revert "socket-proxyd: Add --listener option for listener/destination pairs."	Lennart Poettering
	This reverts commit adcf4c81c58511b67644e17fa743d1729d3c9ccf. We have a better solution for the problem of making two processes run in the same namespace, and --listener is not needed hence and should be dropped. Conflicts: man/systemd-socket-proxyd.xml
2013-11-25	socket-proxyd: Add --listener option for listener/destination pairs.	David Strauss

2013-11-22	event: rename sd_event_get() to sd_event_source_get_event()	Lennart Poettering

2013-11-12	bus: introduce concept of a "default" event loop per-thread and make use of ↵	Lennart Poettering
	it everywhere Try to emphasize a bit that there should be a mapping between event loops and threads, hence introduce a logic that there's one "default" event loop for each thread, that can be queried via "sd_event_default()".
2013-11-07	socket-proxy: actually properly keep track of connections	Lennart Poettering

2013-11-07	socket-proxyd: no need to redefine sockaddr union	Lennart Poettering

2013-11-07	event: make sure we keep a reference to all events we dispatch while we do so.	Lennart Poettering

2013-11-06	socket-proxyd: rework to support multiple sockets and splice()-based ↵	Lennart Poettering
	zero-copy network IO This also drops --ignore-env, which can't really work anymore if we allow multiple fds. Also adds support for pretty printing of peer identities for debug purposes, and abstract namespace UNIX sockets. Also ensures that we never take more connections than a certain limit.
2013-11-06	socket-proxy: clean-up indenting	Lennart Poettering

2013-11-06	clients: unify how we invoke getopt_long()	Lennart Poettering
	Among other things this makes sure we always expose a --version command and show it in the help texts.
2013-10-31	socket-proxyd: Actually, some of those sizes are unsigned.	David Strauss

2013-10-31	fix compiler warnings	Ronny Chevalier
	multiple warnings like src/socket-proxy/socket-proxyd.c: In function ‘transfer_data_cb’: src/socket-proxy/socket-proxyd.c:237:25: warning: format ‘%ld’ expects argument of type ‘long int’, but argument 6 has type ‘size_t’ [-Wformat=] log_debug("Buffer now has %ld bytes full.", c->buffer_filled_len);
2013-10-21	socket-proxyd: Fix-up from previous change to avoid looping on errors.	David Strauss

2013-10-21	socket-proxyd: Use ONESHOT to behave properly with multiple accept() processes.	David Strauss

2013-10-19	socket-proxyd: Remove datagram research TODO. This proxy will not work with ↵	David Strauss
	them.
2013-10-19	socket-proxyd: Comment and log text cleanup.	David Strauss
	* Standardize on "nonblocking" spelling, per Linux man pages. * Clarify that the nonblocking sockets are never in a "blocking" or "unblocked" state, just a "would block" or "ready" state.
2013-10-20	socket-proxyd: initialize variable used in error code path	Kay Sievers

2013-10-18	socket-proxyd: rename from saproxy	Lennart Poettering
	The thing is a daemon, hence needs a "d" prefix. Also, we tend to not abbreviate names of background components unnecessarily, since they are not primary commands people type. Then, the fact that this thing does socket actviation is mostly in implementationd detail for the proxy. Also, do some minor indenting clean-ups and other code updates.