Content-type: text/html Man page of LCRASH

LCRASH

Section: Netkit (1)
Updated: November 2009
Index Return to Main Contents
 

NAME

lcrash - crash machines of a netkit lab  

SYNOPSIS

lcrash [options] [MACHINE-NAME...]

 

DESCRIPTION

The lcrash command can be used to forcedly shutdown all the virtual machines of a Netkit lab. This roughly corresponds to suddenly unplugging them from the power socket. lcrash uses the vcrash command to stop virtual machines (see vcrash(1)).

If a list of MACHINE-NAMEs is provided, only virtual machines with a matching name and that are part of the lab will be crashed. Otherwise, all the machines of the lab are crashed.

The following options are supported by lcrash:

-d DIRECTORY
Crash the Netkit lab that is located inside DIRECTORY. If no -d option is provided, lcrash assumes that the lab is located in the current directory. The path to the lab directory (being that the current directory or one provided by -d) must never contain spaces.

-F
--keep-fs
This option prevents lcrash from deleting virtual machines (COW) filesystems (.disk files). By default, lcrash removes the filesystem after crashing each virtual machine in order to ensure that virtual machines revert to their original state when the lab is restarted.

Notice that the model filesystem is never removed, regardless of the use of this option. See the README file in the Netkit filesystem package for information about COW and model filesystems.

-k
--kill
There are two different ways of crashing a virtual machine. The first one is to send a special message that tells it to immediately shut down. This is also called the mconsole method. The second one is to simply kill running processes that correspond to the virtual machine.
The mconsole method is usually faster, but may be ineffective if a virtual machine has somewhy frozen (in which case it is unable to receive messages). If it happens to fail, the other method (killing processes) is automatically tried. However, killing processes is considered a last resort.
If the mconsole method fails too often, this option can be used to force lcrash to always kill processes. In general, there should be no need to use it.

-l
--list
Show a list of currently running virtual machines after the lab has been crashed. This is useful to check whether all the hosts have been shut down.

-q
--quick
--quiet
Do not check whether virtual machines have actually crashed. This results in a faster lab shutdown, but some hanging processes may be left behind. If this happens, try crashing the lab again without using this option or use vclean (see vclean(1)). This option also slightly reduces output information.

The following standard options are also supported.

-h
--help
Show usage information.

--version
Print information about the installed Netkit release and the host kernel version and exit. If ``<unavailable>'' is printed instead of a version number, then the corresponding information could not be retrieved (for example because a non-standard Netkit kernel or filesystem is being used).

 

ENVIRONMENT VARIABLES

All Netkit commands require that the NETKIT_HOME variable contains the name of the directory Netkit is installed in.

Apart from this, lcrash supports no other environment variables.

 

SEE ALSO

lstart(1), lclean(1), lhalt(1), lrestart(1), linfo(1), ltest(1), vclean(1), vcrash(1), Netkit filesystem README.
    

 

AUTHOR

lcrash script: Stefano Pettini, Massimo Rimondini
This man page: Fabio Ricci, Massimo Rimondini

 

REPORTING BUGS

Report bugs to <netkit.users@list.dia.uniroma3.it> or, alternatively, to <contact@netkit.org>.

Bug reports should always include the following information:

-
Bug description (e.g., expected and actual behaviour).
-
One or more command lines that can be used to reproduce the bug.
-
Name and version of the offending command (e.g., vstart 1.0). You can get the command version by starting it with the option --version.
-
Complete output of the offending command (any --verbose option should be used when producing this report).
-
Version of the Netkit filesystem being used.
-
Version of the Netkit kernel being used.
-
Name and release of the Linux distribution being used on the host machine (e.g., Debian, Ubuntu, Mandrake, Red Hat, Fedora, Gentoo, etc.).
-
Host kernel release and platform. You can get these information by using the `uname -a' command.
-
Description of any patch or changes applied to kernels (host and UML) and filesystems.

 

Index

NAME
SYNOPSIS
DESCRIPTION
ENVIRONMENT VARIABLES
SEE ALSO
AUTHOR
REPORTING BUGS
This document was created by man2html, using the manual pages.
Time: 11:38:55 GMT, January 29, 2010