Linux and UNIX Man Pages

Test Your Knowledge in Computers #639
Difficulty: Easy
NeXTSTEP was based on UNIX.
True or False?
Linux & Unix Commands - Search Man Pages

adt-virt-xenlvm(1) [debian man page]

adt-virt-xenlvm(1)					     Linux Programmer's Manual						adt-virt-xenlvm(1)

adt-virt-xenlvm - autopkgtest virtualisation server using Xen and LVM SYNOPSYS
adt-virt-xenlvm [options] -- [adt-xenlvm options] DESCRIPTION
adt-virt-xenlvm provides an autopkgtest virtualisation server using a Xen virtual machine and LVM snapshots. It adapts the raw functional- ity provided by the adt-xenlvm-* tools for use by autopkgtest. Normally adt-virt-xenlvm will be invoked by adt-run. adt-virt-xenlvm uses adt-xenlvm-with-testbed and adt-xenlvm-on-testbed. The testbed must have previously been set up with adt-xenlvm-set- up. Neither adt-virt-xenlvm nor adt-xenlvm-with-testbed do any locking; it is the the caller's responsibility not to attempt concurrent use of any particular testbed. OPTIONS
--distro=distro Specifies a different distro (ie, the use of a different testbed). --nominum=nominum Specifies a different nominum (ie, the use of a different testbed). --userv Specifies that the adt-xenlvm tools should not be run directly, but rather via userv. The calling user must be permitted to use userv root adt-xenlvm-testbed. In the default configuration, this means being a member of the AdtXenUs group. -- --adt-xenlvm-option=adt-xenlvm-value Following the first occurrence of -- on the adt-virt-xenlvm commandline, any of the values in the adt-xenlvm configuration may be set in the usual way. The arguments are simply passed to adt-virt-xenlvm. See /usr/share/doc/autopkgtest-xenlvm/README.gz for full details of adt-xenlvm. -- -Dvarname=value If --userv was specified, options following the first -- on the adt-virt-xenlvm commandline are passed as option arguments to userv. These should normally be user-defined variable settings using -D which are expected by the autopkgtest-xenlvm/userv-target script. Currently only distro and nominum are expected, and these can be set using adt-virt-xenlvm's own options. -d | --debug Enables debugging output. Probably not hugely interesting. INPUT, OUTPUT AND EXIT STATUS The behaviour of adt-virt-xenlvm is as described by the AutomatedTesting virtualisation regime specification. SEE ALSO
adt-run(1), adt-virt-null(1), adt-virt-chroot(1), /usr/share/doc/autopkgtest/, /usr/share/doc/autopkgtest-xenlvm/README.gz. AUTHORS AND COPYRIGHT
This manpage is part of autopkgtest, a tool for testing Debian binary packages. autopkgtest is Copyright (C) 2006-2007 Canonical Ltd and others. See /usr/share/doc/autopkgtest/CREDITS for the list of contributors and full copying conditions. autopkgtest 2007 adt-virt-xenlvm(1)

Check Out this Related Man Page

LOCK(2) 							System Calls Manual							   LOCK(2)

lockinit, lock, canlock, unlock - shared memory spin lock SYNOPSIS
#include <lock.h> void lockinit(void); void lock(Lock *lk); int canlock(Lock *lk); void unlock(Lock *lk); /* Alef only */ adt Lock { void lock(*Lock); void unlock(*Lock); int canlock(*Lock); }; adt QLock { void lock(*Lock); void unlock(*Lock); int canlock(*Lock); }; adt RWlock { void Rlock(*RWlock); void Runlock(*RWlock); void Wlock(*RWlock); void Wunlock(*RWlock); }; adt Ref { int inc(*Ref); int dec(*Ref); int ref(*Ref); }; DESCRIPTION
These routines are used by processes sharing memory to synchronize using spin locks. Lockinit must be called before the first use of the other routines. Lock blocks until the lock has been obtained. Canlock is non-blocking. It tries to obtain a lock and returns a non-zero value if it was successful, 0 otherwise. Unlock releases a lock. Alef Alef locks have similar functionality, but no special initialization is required. The ADT Lock has functions lock, unlock, and canlock, just like locks in C. QLocks have the same interface but are not spin locks; instead if the lock is taken QLock.lock will suspend execu- tion of the calling task until it is released. Although Locks are the more primitive lock, their use is discouraged and even erroneous for most purposes. For example, Locks cannot syn- chronize between tasks in the same proc. Use QLocks instead. RWlocks manage access to a data structure that has distinct readers and writers. RWlock.Rlock grants read access; RWlock.Runlock releases it. RWlock.Wlock grants write access; RWlock.Wunlock releases it. There may be any number of simultaneous readers, but only one writer. Moreover, if write access is granted no one may have read access until write access is released. Refs manage reference counters. increments the counter and returns the old value; Ref.dec decrements the counter and returns the new value. Ref.ref returns the current value. SOURCE
/sys/src/liblock SEE ALSO
rfork in fork(2) LOCK(2)

Featured Tech Videos