RUMP.HALT(1) BSD General Commands Manual RUMP.HALT(1)NAME
rump.halt -- halt a rump kernel
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
-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.
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
Check Out this Related Man Page
SHMIF(4) BSD Kernel Interfaces Manual SHMIF(4)NAME
shmif -- rump shared memory network interface
rump_pub_shmif_create(const char *path, int *ifnum);
The shmif interface uses a memory mapped regular file as a virtual Ethernet bus. All interfaces connected to the same bus see each others'
Using a memory mapped regular file as a bus has two implications:
1. The bus identifier is not in flat global namespace.
2. Configuring and using the interface is possible without superuser privileges on the host (normal host file access permissions for the
It is not possible to directly access the host networking facilities from a rump virtual kernel using purely shmif. However, traffic can be
routed to another rump kernel instance which provides both shmif and virt(4) networking.
An shmif interface can be created in two ways:
o Programmatically by calling rump_pub_shmif_create(). The bus pathname is passed in path. The number of the newly created interface is
available after a successful call by dereferencing ifnum.
o Dynamically at runtime with ifconfig(8) or equivalent using the create command. In this case the bus path must be configured with
ifconfig(8) linkstr before the interface address can be configured.
Destroying an shmif interface is possible only via ifconfig(8) destroy.
SEE ALSO rump(3), virt(4), ifconfig(8)BSD November 17, 2010 BSD
Unix is great at giving you power were you need it, but what a pain in the rump when you just want to do such a simple thing like file management. I'm going back to Windows, crashing is frustrating, needing to spend 30 min just to zip a file up is crazy. (3 Replies)
Any recommendations for secure storage and file hosting online?
All I need to accomplish is hosting files for clients to download. Would like to auto-delete after 30 days or something of the like.
I've looked at some of the free sites: mediafire, FileDropr/Savr/Factory/Den/Qube- none too... (4 Replies)
Discussion started by: tankcommander
3. Post Here to Contact Site Administrators and Moderators
I am using Ubundu.
I want to know how to run kernel functions in a separate core?
I know about Taskset and it supports only for the application.
Do anybody know any command (or) have any idea about how to do it?
Please help me
Thank you (3 Replies)
We've been using Linode for our virtual Linux hosting services for two years now and could not be more impressed.
One of our Linode nodes is located in Cedar Knolls, New Jersey which was close to the path of Hurricane Sandy. The data center teams were on top of things from the beginning... (0 Replies)
Would you fire this guy?
A man appears to have deleted his entire company with one mistaken piece of code.
By accidentally telling his computer to delete everything in his servers, hosting provider Marco Marsala has seemingly removed all trace of his company and the websites that he looks... (1 Reply)