depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2006-12-05	* Some renaming.	Eelco Dolstra	1	-6/+6

2006-12-05	* Allow unprivileged users to run the garbage collector and to do	Eelco Dolstra	1	-0/+22
	`nix-store --delete'. But unprivileged users are not allowed to ignore liveness. * `nix-store --delete --ignore-liveness': ignore the runtime roots as well.
2006-12-05	* The determination of the root set should be made by the privileged	Eelco Dolstra	1	-17/+12
	process, so forward the operation. * Spam the user about GC misconfigurations (NIX-71). * findRoots: skip all roots that are unreadable - the warnings with which we spam the user should be enough.
2006-12-04	* Add indirect root registration to the protocol so that unprivileged	Eelco Dolstra	1	-0/+10
	processes can register indirect roots. Of course, there is still the problem that the garbage collector can only read the targets of the indirect roots when it's running as root...
2006-12-04	* Not every OS knows about SIGPOLL.	Eelco Dolstra	1	-0/+5

2006-12-04	* Handle exceptions and stderr for all protocol functions.	Eelco Dolstra	1	-19/+54
	* SIGIO -> SIGPOLL (POSIX calls it that). * Use sigaction instead of signal to register the SIGPOLL handler. Sigaction is better defined, and a handler registered with signal appears not to interrupt fcntl(..., F_SETLKW, ...), which is bad.
2006-12-04	* Daemon mode (`nix-worker --daemon'). Clients connect to the server	Eelco Dolstra	1	-33/+150
	via the Unix domain socket in /nix/var/nix/daemon.socket. The server forks a worker process per connection. * readString(): use the heap, not the stack. * Some protocol fixes.
2006-12-03	* Don't run setuid root when build-users is empty.	Eelco Dolstra	1	-25/+49
	* Send startup errors to the client.
2006-12-03	* Handle a subtle race condition: the client closing the socket	Eelco Dolstra	1	-2/+30
	between the last worker read/write and the enabling of the signal handler.
2006-12-03	* Some hardcore magic to handle asynchronous client disconnects.	Eelco Dolstra	1	-1/+37
	The problem is that when we kill the client while the worker is building, and the builder is not writing anything to stderr, then the worker never notice that the socket is closed on the other side, so it just continues indefinitely. The solution is to catch SIGIO, which is sent when the far side of the socket closes, and simulate an normal interruption. Of course, SIGIO is also sent every time the client sends data over the socket, so we only enable the signal handler when we're not expecting any data...
2006-12-03	* Some hackery to propagate the worker's stderr and exceptions to the	Eelco Dolstra	1	-95/+150
	client.
2006-12-03	* Run the worker in a separate session to prevent terminal signals	Eelco Dolstra	1	-0/+6
	from interfering.
2006-12-02	* Move addTempRoot() to the store API, and add another function	Eelco Dolstra	1	-0/+13
	syncWithGC() to allow clients to register GC roots without needing write access to the global roots directory or the GC lock.
2006-12-02	* Remove queryPathHash().	Eelco Dolstra	1	-1/+13
	* Help for nix-worker.
2006-12-01	* Merge addToStore and addToStoreFixed.	Eelco Dolstra	1	-12/+5
	* addToStore now adds unconditionally, it doesn't use readOnlyMode. Read-only operation is up to the caller (who can call computeStorePathForPath).
2006-12-01	* Right name.	Eelco Dolstra	1	-2/+2

2006-12-01	* More operations.	Eelco Dolstra	1	-2/+21
	* addToStore() and friends: don't do a round-trip to the worker if we're only interested in the path (i.e., in read-only mode).
2006-11-30	* More remote operations.	Eelco Dolstra	1	-9/+51
	* Added new operation hasSubstitutes(), which is more efficient than querySubstitutes().size() > 0.
2006-11-30	* More operations.	Eelco Dolstra	1	-1/+27

2006-11-30	* First remote operation: isValidPath().	Eelco Dolstra	1	-2/+31

2006-11-30	* When NIX_REMOTE is set to "slave", fork off nix-worker in slave	Eelco Dolstra	1	-23/+12
	mode. Presumably nix-worker would be setuid to the Nix store user. The worker performs all operations on the Nix store and database, so the caller can be completely unprivileged. This is already much more secure than the old setuid scheme, since the worker doesn't need to do Nix expression evaluation and so on. Most importantly, this means that it doesn't need to access any user files, with all resulting security risks; it only performs pure store operations. Once this works, it is easy to move to a daemon model that forks off a worker for connections established through a Unix domain socket. That would be even more secure.
2006-11-30	* Skeleton of the privileged worker program.	Eelco Dolstra	1	-0/+63
	* Some refactoring: put the NAR archive integer/string serialisation code in a separate file so it can be reused by the worker protocol implementation.