notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
non port: Tools/portbuild/scripts/clean-chroot
SVNWeb

Number of commits found: 19

Sun, 24 Apr 2011
[ 16:37 flz search for other commits by this committer ] Original commit  (Only the first 10 of 72 ports in this commit are shown above. View all ports for this commit)
Remove portbuild scripts from pcvs, as they now live in svn/projects.
Wed, 1 Dec 2010
[ 02:27 linimon search for other commits by this committer ] Original commit 
Although I was going to try to avoid it, it turns out that it is
impossble to have merely "server.conf" and "client.conf" control
everything on a head node.  Some pieces must be refactored into
"common.conf".
Fri, 25 Jun 2010
[ 23:04 linimon search for other commits by this committer ] Original commit 
Generalize the packge building scripts to be able to be run on more than
one 'head' node, rather than just pointyhat itself.

Constants are factored out into installation-specific files known as
portbuild/conf/server.conf and portbuild/conf/client.conf.  There is
only one server.conf file.  Individual <arch> directories may have
their own client.conf files, or may symlink to ../conf/client.conf.

While here, rework the code a bit to parameterize arch-specific tasks.

Feature safe:   yes
Mon, 16 Nov 2009
[ 00:16 linimon search for other commits by this committer ] Original commit 
Harden these a bit: make them identify on which host they were running;
skip unncessary steps.
Sat, 26 Jul 2008
[ 14:12 kris search for other commits by this committer ] Original commit 
* Cleanup
* Catch up to build ID directory changes
* Improved support for ZFS
* Desupport X11BASE
Sun, 29 Jul 2007
[ 20:27 kris search for other commits by this committer ] Original commit 
Support builds using zfs and tmpfs backing store

zfs:

* Enabled by use_zfs=1 in portbuild.conf

* Populate build chroots by cloning a zfs snapshot instead of maintaining
  many duplicate copies.  In principle this is very efficient since
  everything is copy-on-write and zfs snapshot creation is almost
  instantaneous.  There might be additional overheads from building on zfs
  though.  Currently the snapshot base is hard-wired to y/${branch}@base
  but should be parametrized.  This also must be populated beforehand, e.g.
  during machine startup

* Clean build chroots by just destroying the snapshot.

tmpfs:

* Enabled by use_tmpfs=1 and tmpfs_size in portbuild.conf

* The previous md strategy of mounting in used/, populating and then
  remounting (to avoid possible races from multiple builds claiming the
  same chroot) doesn't work here because tmpfs instances are destroyed at
  umount.  I am not entirely sure the simpler approach is free from races.
Sun, 18 Feb 2007
[ 08:57 kris search for other commits by this committer ] Original commit 
Also attempt to clean /root/.ccache in case it is in use.  When cleaning
on a machine that has use_md_swap=1, allow for the possibility of reusing
a md between builds if md_persistent=1.  This requires a patch from pjd
to support BIO_DELETE in md devices, but it is a big optimization when
it can be used.
Thu, 14 Sep 2006
[ 05:14 kris search for other commits by this committer ] Original commit 
Go back to force unmounting because not doing so was too unreliable.
Mon, 3 Apr 2006
[ 04:41 kris search for other commits by this committer ] Original commit 
Clean up linprocfs on amd64 as well.
Sat, 11 Feb 2006
[ 10:05 kris search for other commits by this committer ] Original commit 
* In kill_procs(), pass in the directory and mountpoint as separate
  arguments (cosmetic)

* Detect if a chroot was used to run a jailed build, and first attempt
  to gracefully shut it down by killing everything within using pgrep(1)
  This has a much higher chance of succeeding that relying on fstat to
  identify processes that might interfere with our attempts to clean up
  mountpoints, which is fragile (libkvm-dependent), and inherently
  unreliable at best.
Fri, 3 Feb 2006
[ 20:08 kris search for other commits by this committer ] Original commit 
Instead of passing in a "noclean" boolean, pass in a "clean" level:
  0 = don't clean chroot
  1 = sanitize commonly-modified directories
  2 = remove entire chroot
Sun, 22 Jan 2006
[ 04:54 kris search for other commits by this committer ] Original commit 
Pull in buildenv for LOCALBASE/X11BASE locations

Don't bother cleaning up doc mounts, they are not needed.
Tue, 11 Oct 2005
[ 03:45 kris search for other commits by this committer ] Original commit 
* Add support for use_md_swap
[ 03:27 kris search for other commits by this committer ] Original commit 
Silence some possible errors from chflags -R
Sat, 12 Feb 2005
[ 03:38 kris search for other commits by this committer ] Original commit 
* Instead of using umount -f to unmount things, first use fstat to
look for processes holding open references within the FS and kill
them, then use regular umount.  This is necessary now that devfs
cannot be force-unmounted, and has the benefit that processes can't
hang around holding references to files between port builds.

* Reduce possibility for error by testing for presence of executable
ldconfig inside the chroot before attempting to run it (e.g. it may not
be there if the chroot was not completely initialized)
Sun, 9 Jan 2005
[ 10:21 krion search for other commits by this committer ] Original commit  (Only the first 10 of 28 ports in this commit are shown above. View all ports for this commit)
Remove traling spaces.
Sun, 5 Dec 2004
[ 00:15 kris search for other commits by this committer ] Original commit 
Be silent about attempts to unmount filesystems from within the chroot
Sun, 26 Sep 2004
[ 21:59 kris search for other commits by this committer ] Original commit 
Refuse to "clean" / if something goes wrong upstream and we are passed
the wrong path

Approved by:    portmgr (self)
Wed, 14 Jul 2004
[ 10:45 kris search for other commits by this committer ] Original commit 
Clean up the specified chroot (umount filesystems, and scrub the
directories likely to contain changed files).

Number of commits found: 19