Hello On Sun, Apr 17, 2005 at 06:08:30PM +0200, Daniel Hermann wrote: > Hi Ola, > > On Thu, Apr 14, 2005 at 10:04:04PM +0200, Ola Lundqvist wrote: > > > > On Thu, Apr 14, 2005 at 07:31:08PM +0200, Daniel Hermann wrote: > > > > > looked over and compared to the outputs of "<command> --help" to find > > > features no longer existing or changed in the alpha branch. > > > > > > I can definitely say that two things documented in the man-page of > > > vserver don't work any more: > > > - Option "--nodev" > > > - subcommand "service" (vserver ... service ... start/stop) > > > > True. I have forgotten that I wrote that manpage. :) > > > > You wrote them? I ask because a different author (Klavs Klavsen) is > mentioned there.
Well good, then my memory is not too bad. > > > Is it useful for you to file detailed information or to write > > > patches against the man-pages? > > > > If you can provide patches that is of course appriciated. > > > > instead of producing patches I used the "--help" output of vserver and > vserver-build to produce new man pages. I have sent them to the > vserver list and also attach them to this mail. Maybe they are useful > for somebody. Thanks a lot. Then Enrico will probably incorporate it instead. > BTW: What version of util-vserver are you planning to release with > sarge? Latest available that is stable enough to build on all arches and that will work good enough. It depends much on when sarge is frozen. Regards, // Ola > regards > > Daniel > > -- > ----------------------------------------------------------------- > Daniel Hermann, Institut fuer Theorie der Kondensierten Materie > Universitaet Karlsruhe Tel: ++49 (0)721 608-3588 > Postfach 6980 Fax: ++49 (0)721 608-7779 > 76128 Karlsruhe, Germany email: [EMAIL PROTECTED] > ----------------------------------------------------------------- > =head1 NAME > > vserver - controls and builds virtual servers > > =head1 SYNOPSIS > > vserver [options] vserver-name command [args] > > =head1 DESCRIPTION > > The vserver utility enables you to control different aspects of your > vservers, such as stopping and starting them, installing packages > inside the vservers, or building new vservers. > > =head1 COMMANDS > > Possible commands are: > > B<start> [--nodeps] <start-vservers-opts>* > starts the specified vserver > > B<stop> [--nodeps] <start-vservers-opts>* > stops the specified vserver > > B<restart> restarts the specified vserver; this is the subsequent > execution of a synchronized 'stop' and a 'start' > > B<condrestart> restarts the vserver when it is running already > > B<suexec> <user> <shell-command> <args*> > executes a command as the specified user in the vserver > > B<exec> <shell-command> <args*> > executes a command as root in the vserver > > B<enter> executes the configured shell in the vserver > > B<chkconfig> <chkconfig-options*> > modifies the init-system; currently, only Red Hat's > chkconfig is supported > > B<running> succeeds iff the vserver is running > > B<status> gives out some human readable status information about > the vserver, and succeeds iff the vserver is running > > B<build> <buildopts>* > builds a new vserver from scratch (please refer to > B<vserver-build>(8) for details) > > B<unify> [-R] (de)unify vserver > > B<pkg install> <pkg> > installs package(s) in the vserver > > B<apt-get>,B<apt-config>,B<apt-cache> <apt-opts>* > execute the apt-* command for the given vserver > > B<rpm> <rpm-opts>* > execute the rpm command for the given vserver > > B<pkgmgmt externalize|internalize> [-y] > externalize or internalize the package-management for > the given vserver. 'Externalize' means that package > metadata and management tools (apt-get,rpm) are living > in the host, while 'internalize' means that data and > programs from the vserver will be used. > > B<unify> <vunify-opts>* > unify the vserver with its reference vserver(s). > > =head1 OPTIONS > > B<--help> > show help > > B<-s | --sync> > start/stop vserver synchronously > > B<-v | --verbose> > detailed output > > B<--silent> > cuts most informative messages > > =head1 FILES > > I</etc/vservers/.default/> > default configuration common to all vservers > > I</etc/vservers/*/> > separate configuration subdirectory for each vserver > > I</var/lib/vservers> > default location of vservers > > =head1 SEE ALSO > > B<vserver-build>(8), B<vserver-copy>(8), B<vserver-stat>(8), > B<vtop>(8), B<vps>(8), B<vpstree>(8), > B<chcontext>(8), B<chbind>(8), B<reducecap>(8) > > =head1 BUGS > > Please report bugs to [EMAIL PROTECTED] > > =head1 AUTHORS > > manual page written by Daniel Hermann <[EMAIL PROTECTED]> > using output of "vserver --help" > > =head1 NAME > > vserver-build - build new vserver with vserver ... build > > =head1 SYNOPSIS > > vserver vserver-name build -m <method> [options] [cfg-options] > [--] [method-args] > > =head1 METHODS > > Possible methods are: > > B<legacy> the "old" copy-all-from-host method, which requires the > old legacy vserver-legacy script; with this method > the cfg-options will be ignored > > B<copy> the copy-all-from-host method which uses the recent > configuration scheme > > B<apt-rpm> ... -- -d <distribution> > installs the base-packages of the given distribution with > help of 'vapt-get' > > B<yum> ... -- -d <distribution> > installs the base-packages of the given distribution with > help of 'vyum' > > B<rpm> ... -- [-d <distribution>] > --empty | ([--force] [--nodeps] <manifest>)+ > installs lists of rpm-packages > > B<skeleton> ... -- [<cmd> <args>*] > installs a minimal skeleton filesystem, creates the > configuration file and calls an optional command then > > B<debootstrap> ... -- -d <distrib> [-m <mirror> ] [-- <debootstrap-opts>*] > bootstraps the vserver with Debian's 'debootstrap' package > > =head1 OPTIONS > > B<--force> remove/rename already existing vservers with the same name > > B<--rootdir> <dir> > vserver root directory [default: /vservers] > > B<--pkgbase> <dir> > package base directory [default: /vservers/.pkg] > > =head1 CFG-OPTIONS > > B<--context> the static context of the vserver [default: none; a dynamic > context will be assumed] > > B<--confdir> vserver-specific configuration directory > [default: /etc/vservers/<vserver-name>] > > B<--lockfile> <filename> > lock file [default: /var/run/vservers/<vserver-name>] > > B<--hostname> <hostname> > > B<--netdev> <device> > > B<--netbcast> <broadcast> > > B<--netmask> <netmask> | --netprefix <prefixlen> > sets the default netmask (a.b.c.d quadruple) or prefixlen > (length of the interface) > > B<--interface> [<name-suffix>=][<device>:]<ip>[/<mask|prefixlen>] > declares an network-interface; this option can be specified > multiple times > > B<--flags> <flags>+ > sets comma-separated list of flags; possible flags are > lock: Prevent the vserver from setting new security > context > sched: Merge scheduler priority of all processes in the > vserver so that it acts a like a single > one (kernel 2.4 only). > nproc: Limit the number of processes in the vserver > according to ulimit (instead of a per user limit, > this becomes a per vserver limit) > private: No other process can join this security context. > Even root > > B<--initstyle> <style> > configures the initstyle (e.g. minit,sysv,plain) > > > =head1 SEE ALSO > > B<vserver>(8), B<vserver-copy>(8), B<vserver-stat>(8), > B<vtop>(8), B<vps>(8), B<vpstree>(8), > B<chcontext>(8), B<chbind>(8), B<reducecap>(8) > > =head1 BUGS > > Please report bugs to [EMAIL PROTECTED] > > =head1 AUTHORS > > manual page written by Daniel Hermann <[EMAIL PROTECTED]> > using output of "vserver-build --help" > all: vserver.8 vserver-build.8 > > %.8: %.pod > pod2man --section=8 --center=util-vserver --release=util-vserver $< $@ > > vserver.8: vserver.pod > vserver-build.8: vserver-build.pod -- --------------------- Ola Lundqvist --------------------------- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | +46 (0)54-10 14 30 +46 (0)70-332 1551 | | http://www.opal.dhs.org UIN/icq: 4912500 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
