search for: vendetta

...jail rc.d script, which allows user to set jail nice value. It doesn't change any default behaviour. Can that make it to the trees? Patch attached. -- Jan Srzednicki :: http://wrzask.pl/ "Remember, remember, the fifth of November" -- V for Vendetta -------------- next part -------------- A non-text attachment was scrubbed... Name: jail.diff Type: text/x-diff Size: 1053 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080224/b78f5b5b/jail.bin

...jail rc.d script, which allows user to set jail nice value. It doesn't change any default behaviour. Can that make it to the trees? Patch attached. -- Jan Srzednicki :: http://wrzask.pl/ "Remember, remember, the fifth of November" -- V for Vendetta -------------- next part -------------- A non-text attachment was scrubbed... Name: jail.diff Type: text/x-diff Size: 1053 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080224/b78f5b5b/jail.bin

Hey, I have a Compaq T2000 UPS that I use to power my firewall, dmz, and two internal machines and I've just started implementing UPS monitoring to shut the systems down in the event of an outage instead of relying on me, but I've run into a snag. Reading the documentation, it seems the client has to contact the server. The problem is I really don't want to open a port form the

When somebody is hammering on the system, I want to be able to detect who''s doing it, and hopefully even what they''re doing. I can''t seem to find any way to do that. Any suggestions? Everything I can find ... iostat, nfsstat, etc ... AFAIK, just show me performance statistics and so forth. I''m looking for something more granular. Either *who* the

CentOS mailing list, Thank you all for answering my questions and being so supportive over the last few months as I was running CentOS on my home machine. I have switched over to Ubuntu, and I will be devoting my learning efforts to that distribution from this point on. However, while I'm sure a new distribution will have the inevitable learning curve, a lot of the tips and tricks I

All, As much as I hate to ask, how is this project coming along? We are approaching the 4 month post-release point... -David -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20110404/1e9862bd/attachment-0005.html>

This adds support for vhost-net virtio kernel backend. To enable (assuming device eth2): 1. enable promisc mode or program guest mac in device eth2 2. disable tso, gso, lro, jumbo frames on the card (disabling lro + jumbo frames should be sufficient, haven't tested this) 3. add vhost=eth2 to -net flag 4. run with CAP_NET_ADMIN priviledge (e.g. root) This patch is RFC, but works without

This adds support for vhost-net virtio kernel backend. To enable (assuming device eth2): 1. enable promisc mode or program guest mac in device eth2 2. disable tso, gso, lro, jumbo frames on the card (disabling lro + jumbo frames should be sufficient, haven't tested this) 3. add vhost=eth2 to -net flag 4. run with CAP_NET_ADMIN priviledge (e.g. root) This patch is RFC, but works without

On Tue, 2015-03-24 at 09:38 +0100, Niki Kovacs wrote: > Le 24/03/2015 08:34, John R Pierce a ?crit : > > I'd be looking at something like TinyLinux or DamnSmallLinux on those. > > I don't want anything else than CentOS for the job. > > I used to install my own heavily customized version of Slackware on > these machines (http://www.microlinux.fr/slackware/), but