depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2012-08-01	Count bytes freed deleting unused links	Eelco Dolstra	1	-1/+1

2012-08-01	Drop the block count in the garbage collector	Eelco Dolstra	1	-2/+1

2012-07-23	Garbage collect unused links in /nix/store/.links	Eelco Dolstra	1	-0/+2
	Incremental optimisation requires creating links in /nix/store/.links to all files in the store. However, this means that if we delete a store path, no files are actually deleted because links in /nix/store/.links still exists. So we need to check /nix/store/.links for files with a link count of 1 and delete them.
2012-07-23	Automatically optimise the Nix store when a new path is added	Eelco Dolstra	1	-0/+7
	Auto-optimisation is enabled by default. It can be turned off by setting auto-optimise-store to false in nix.conf.
2012-07-23	optimiseStore(): Use a content-addressed file store in /nix/store/.links	Eelco Dolstra	1	-1/+1
	optimiseStore() now creates persistent, content-addressed hard links in /nix/store/.links. For instance, if it encounters a file P with hash H, it will create a hard link P' = /nix/store/.link/<H> to P if P' doesn't already exist; if P' exist, then P is replaced by a hard link to P'. This is better than the previous in-memory map, because it had the tendency to unnecessarily replace hard links with a hard link to whatever happened to be the first file with a given hash it encountered. It also allows on-the-fly, incremental optimisation.
2012-07-18	Use "#pragma once" to prevent repeated header file inclusion	Eelco Dolstra	1	-5/+1

2012-07-17	Add function queryPathFromHashPart()	Eelco Dolstra	1	-0/+3
	To implement binary caches efficiently, Hydra needs to be able to map the hash part of a store path (e.g. "gbg...zr7") to the full store path (e.g. "/nix/store/gbg...kzr7-subversion-1.7.5"). (The binary cache mechanism uses hash parts as a key for looking up store paths to ensure privacy.) However, doing a search in the Nix store for /nix/store/<hash>* is expensive since it requires reading the entire directory. queryPathFromHashPart() prevents this by doing a cheap database lookup.
2012-06-27	nix-store -r: do substitutions in parallel	Eelco Dolstra	1	-1/+1
	I.e. when multiple non-derivation arguments are passed to ‘nix-store -r’ to be substituted, do them in parallel.
2012-05-29	Reserve some disk space for the garbage collector	Eelco Dolstra	1	-1/+1
	We can't open a SQLite database if the disk is full. Since this prevents the garbage collector from running when it's most needed, we reserve some dummy space that we can free just before doing a garbage collection. This actually revives some old code from the Berkeley DB days. Fixes #27.
2012-03-26	Make the garbage collector more concurrent	Eelco Dolstra	1	-4/+5
	Make the garbage collector more concurrent by deleting valid paths outside the region where we're holding the global GC lock. This should greatly reduce the time during which new builds are blocked, since the deletion accounts for the vast majority of the time spent in the GC. To ensure that this is safe, the valid paths are invalidated and renamed to some arbitrary path while we're holding the lock. This ensures that we when we finally delete the path, it's not a (newly) valid or locked path.
2011-12-16	* Sync with the trunk.	Eelco Dolstra	1	-1/+3

2011-12-16	* importPath() -> importPaths(). Because of buffering of the input	Eelco Dolstra	1	-1/+3
	stream it's now necessary for the daemon to process the entire sequence of exported paths, rather than letting the client do it.
2011-11-06	Include all outputs of derivations in the closure of explicitly-passed ↵	Shea Levy	1	-0/+2
	derivation paths This required adding a queryOutputDerivationNames function in the store API
2011-09-12	* Ouch. A store upgrade could cause a substituter to be triggered,	Eelco Dolstra	1	-1/+1
	causing a deadlock.
2011-07-20	* Fix a huuuuge security hole in the Nix daemon. It didn't check that	Eelco Dolstra	1	-0/+5
	derivations added to the store by clients have "correct" output paths (meaning that the output paths are computed by hashing the derivation according to a certain algorithm). This means that a malicious user could craft a special .drv file to build any desired path in the store with any desired contents (so long as the path doesn't already exist). Then the attacker just needs to wait for a victim to come along and install the compromised path. For instance, if Alice (the attacker) knows that the latest Firefox derivation in Nixpkgs produces the path /nix/store/1a5nyfd4ajxbyy97r1fslhgrv70gj8a7-firefox-5.0.1 then (provided this path doesn't already exist) she can craft a .drv file that creates that path (i.e., has it as one of its outputs), add it to the store using "nix-store --add", and build it with "nix-store -r". So the fake .drv could write a Trojan to the Firefox path. Then, if user Bob (the victim) comes along and does $ nix-env -i firefox $ firefox he executes the Trojan injected by Alice. The fix is to have the Nix daemon verify that derivation outputs are correct (in addValidPath()). This required some refactoring to move the hash computation code to libstore.
2010-12-06	* `nix-store --verify --check-contents': don't hold the global GC lock	Eelco Dolstra	1	-0/+3
	while checking the contents, since this operation can take a very long time to finish. Also, fill in missing narSize fields in the DB while doing this.
2010-11-17	* Add an operation `nix-store -q --size'.	Eelco Dolstra	1	-0/+1

2010-11-16	* Store the size of a store path in the database (to be precise, the	Eelco Dolstra	1	-6/+3
	size of the NAR serialisation of the path, i.e., `nix-store --dump PATH'). This is useful for Hydra.
2010-08-31	`nix-store --verify' improvements:	Eelco Dolstra	1	-2/+8
	* If a path has disappeared, check its referrers first, and don't try to invalidate paths that have valid referrers. Otherwise we get a foreign key constraint violation. * Read the whole Nix store directory instead of statting each valid path, which is slower. * Acquire the global GC lock.
2010-06-21	* Okay, putting a lock on the temporary directory used by importPath()	Eelco Dolstra	1	-0/+2
	doesn't work because the garbage collector doesn't actually look at locks. So r22253 was stupid. Use addTempRoot() instead. Also, locking the temporary directory in exportPath() was silly because it isn't even in the store.
2010-05-04	* Allow unprivileged users to do `nix-store --clear-failed-paths' and	Eelco Dolstra	1	-3/+0
	`nix-store --query-failed-paths'.
2010-04-26	* Added a command `nix-store --clear-failed-paths <PATHS>' to clear	Eelco Dolstra	1	-0/+5
	the "failed" status of the given store paths. The special value `*' clears all failed paths.
2010-04-26	* Add an command `nix-store --query-failed-paths' to list the cached	Eelco Dolstra	1	-0/+4
	failed paths (when using the `build-cache-failure' option).
2010-02-24	* Refactor the upgrade / database initialisation logic a bit.	Eelco Dolstra	1	-3/+1

2010-02-24	* A function to query just the database id of a valid path.	Eelco Dolstra	1	-0/+2

2010-02-24	* Disable fsync() in SQLite if the fsync-metadata option is set to	Eelco Dolstra	1	-3/+0
	false. * Change the default for `fsync-metadata' to true. * Disable `fsync-metadata' in `make check'.
2010-02-22	* Get derivation outputs from the database instead of the .drv file,	Eelco Dolstra	1	-0/+3
	which requires more I/O.
2010-02-22	* Revert r19650 (implement gc-keep-outputs by looking for derivations	Eelco Dolstra	1	-2/+7
	with the same name as the output) and instead use the DerivationOutputs table in the database, which is the correct way to to do things.
2010-02-22	* Put the derivation outputs in the database. This is useful for the	Eelco Dolstra	1	-0/+1
	garbage collector.
2010-02-19	* Foreign key support in SQLite is not a persistent setting, so enable	Eelco Dolstra	1	-0/+2
	it at startup. * Implement negative caching. Now `make check' passes.
2010-02-19	* Implement more stuff.	Eelco Dolstra	1	-0/+5

2010-02-19	* Implement registerValidPath().	Eelco Dolstra	1	-1/+5

2010-02-18	* Implemented queryReferrers().	Eelco Dolstra	1	-2/+1

2010-02-18	* Implement queryPathInfo().	Eelco Dolstra	1	-2/+3

2010-02-18	* Implement isValidPath().	Eelco Dolstra	1	-10/+5

2010-02-18	* Some wrapper objects to ensure that SQLite objects are properly	Eelco Dolstra	1	-4/+36
	destroyed.
2010-02-18	* Convert the Nix database to SQLite.	Eelco Dolstra	1	-1/+7

2010-01-29	* Added an option "fsync-metadata" to fsync() changes to	Eelco Dolstra	1	-0/+5
	/nix/var/nix/db. * Removed the function writeStringToFile since it does (almost) the same thing as writeFile.
2010-01-25	* Make the garbage collector do the right thing when `gc-keep-outputs'	Eelco Dolstra	1	-0/+2
	is enabled by not depending on the deriver.
2009-11-23	* Made the garbage collector a lot faster. It no longer computes the	Eelco Dolstra	1	-5/+6
	complete set of live and dead paths before starting the actual deletion, but determines liveness on demand. I.e. for any path in the store, it first tries to delete all the referrers, and then the path itself. This means that the collector can start deleting paths almost immediately.
2009-10-22	* Remove a prototype for a function that no longer exists.	Eelco Dolstra	1	-3/+0

2009-06-13	* Canonicalise timestamps in the Nix store to 1 (1970-01-01 00:00:01	Eelco Dolstra	1	-2/+2
	UTC) rather than 0 (00:00:00). 1 is a better choice because some programs use 0 as a special value. For instance, the Template Toolkit uses a timestamp of 0 to denote the non-existence of a file, so it barfs on files in the Nix store (see template-toolkit-nix-store.patch in Nixpkgs). Similarly, Maya 2008 fails to load script directories with a timestamp of 0 and can't be patched because it's closed source. This will also shut up those "implausibly old time stamp" GNU tar warnings.
2009-03-28	* Don't use the non-standard __gnu_cxx::stdio_filebuf class.	Eelco Dolstra	1	-8/+1

2009-03-25	* Negative caching, i.e. caching of build failures. Disabled by	Eelco Dolstra	1	-0/+7
	default. This is mostly useful for Hydra.
2008-12-16	* nix-store --verify: repair bad hash fields in the metadata file.	Eelco Dolstra	1	-1/+1

2008-12-03	* addToStore() in nix-worker: don't write the NAR dump received from	Eelco Dolstra	1	-0/+7
	the client to a temporary directory, as that is highly inefficient.
2008-12-03	* Pass HashType values instead of strings.	Eelco Dolstra	1	-1/+1

2008-12-03	* Unify the treatment of sources copied to the store, and recursive	Eelco Dolstra	1	-3/+3
	SHA-256 outputs of fixed-output derivations. I.e. they now produce the same store path: $ nix-store --add x /nix/store/j2fq9qxvvxgqymvpszhs773ncci45xsj-x $ nix-store --add-fixed --recursive sha256 x /nix/store/j2fq9qxvvxgqymvpszhs773ncci45xsj-x the latter being the same as the path that a derivation derivation { name = "x"; outputHashAlgo = "sha256"; outputHashMode = "recursive"; outputHash = "..."; ... }; produces. This does change the output path for such fixed-output derivations. Fortunately they are quite rare. The most common use is fetchsvn calls with SHA-256 hashes. (There are a handful of those is Nixpkgs, mostly unstable development packages.) * Documented the computation of store paths (in store-api.cc).
2008-09-17	* Some refactoring. Better output with `-v' for --use-atime.	Eelco Dolstra	1	-2/+5

2008-09-17	* Garbage collector: added an option `--use-atime' to delete paths in	Eelco Dolstra	1	-2/+1
	order of ascending last access time. This is useful in conjunction with --max-freed or --max-links to prefer deleting non-recently used garbage, which is good (especially in the build farm) since garbage may become live again. The code could easily be modified to accept other criteria for ordering garbage by changing the comparison operator used by the priority queue in collectGarbage().