rump.halt(1) [netbsd man page]

RUMP.HALT(1)						    BSD General Commands Manual 					      RUMP.HALT(1)

NAME

     rump.halt -- halt a rump kernel

SYNOPSIS

     rump.halt [-dhn]

DESCRIPTION

     The rump.halt utility exits a rump kernel.  The file system cache, if present, is flushed.  Since a rump kernel does not control its clients,
     they are not directly affected by rump.halt.  However, they will be unable to request further services from the halted rump kernel.

     The options are as follows:

     -d      Create a core dump.  The core file is saved according to standard userland program coredump rules, and can be later examined with a
	     debugger.

     -h      By default the process hosting the rump kernel exits.  Using this option shuts down rump kernel activity, but does not cause the
	     hosting process to exit.

     -n      Do not flush the file system cache.  This option should be used with extreme caution.  It can be used if a virtual disk or a virtual
	     processor is virtually on fire.

SEE ALSO

     rump(3)

HISTORY

     The rump.halt command appeared in NetBSD 6.0.

CAVEATS

     While using -h makes it impossible to issue further system calls, it does not necessarily stop all activity in a rump kernel.  It is recom-
     mended this option is used only for debugging purposes.

BSD
								 December 12, 2010							       BSD

RUMP_NFS(8)						    BSD System Manager's Manual 					       RUMP_NFS(8)

NAME

     rump_nfs -- mount a nfs share with a userspace server

SYNOPSIS

     file-system PUFFS
     pseudo-device putter

     rump_nfs [options] share mountpoint

DESCRIPTION

     NOTE! This manual page describes features specific to the rump(3) file server.  Please see mount_nfs(8) for a full description of the avail-
     able command line options.

     The rump_nfs utility can be used to mount nfs file systems.  It uses rump(3) and p2k(3) to facilitate running the file system as a server in
     userspace.  As opposed to mount_nfs(8), rump_nfs does not use file system code within the kernel and therefore does not require kernel sup-
     port except puffs(4).  Apart from a minor speed penalty there is no downside with respect to in-kernel code.

     Even though the rump_nfs file system client runs within a virtual rump kernel in userspace, it uses host network services (by means of ``rump
     sockin'').  This means that regardless of whether using rump_nfs or mount_nfs(8), the same network configurations will be used.  Currently,
     ``sockin'' supports IPv4.

     To use rump_nfs via mount(8), the flags -o rump and -t nfs should be given.  Similarly, rump_nfs is used instead of mount_nfs(8) if ``rump''
     is added to the options field of fstab(5).

SEE ALSO

     p2k(3), puffs(3), rump(3), mount_nfs(8)

HISTORY

     The rump_nfs utility first appeared in NetBSD 5.0.

BSD
								 November 21, 2010							       BSD