qarsh.git - qarsh - a remote shell for testing environments

	Commit message (Collapse)	Author	Age	Files	Lines
*	Don't let systemd block SIGPIPE on us	Nathan Straz	2013-09-23	1	-0/+1
\| \| \| \| \| \| \|	We do ignore SIGPIPE inside qarshd so we can handle the error and continue. We do want commands we run to receive SIGPIPE by default so they may die if they don't handle SIGPIPE.
*	Handle stdin pipe closing on us	Nathan Straz	2013-09-19	1	-1/+0
\| \| \| \| \| \| \|	If xiogen is flooding requests across qarsh and xdoio decides to stop, we need to handle that gracefully. Also, making the pipe non-blocking was not a good idea, xdoio gets the read error EAGAIN and stops there.
*	Send all server side error messages to stderr	Nathan Straz	2013-09-11	1	-0/+1
\| \| \| \|	This should get sent to the journal or syslog
*	Keep SIGPIPE working as expected	Nathan Straz	2013-05-21	1	-0/+1
\| \| \| \| \|	It turns out the systemd maintainers thought it would be good to ignore SIGPIPE by default. I don't agree.
*	Convert to systemd socket activated services	Nathan Straz	2013-05-14	1	-0/+6
	qarshd and btimed will now start directly from systemd xinetd is no longer needed