search for: msg00228

...tions active except DHCP-Server (customer has its own), mainly: DNS, NAT, firewall, bandwidth management, user management (IP+MAC matching), ip accounting, transparent smtp proxy with a/v, checking for unpatched windowses (vulncheck.pl, see here: http://cert.uni-stuttgart.de/archive/bugtraq/2004/05/msg00228.html) and some other experimental security programs - user list polled from external data source (postgres) provided by customer Active measurements (from a normal machine located in LAN): - average RTT (ping) to next hop (provider''s router): 20ms, packet loss 0.1% - RTT jumps over 100ms...

...bly get them from? I found a couple of patch series posted onto the mailing list before but it''s not cleared what version or what tree they should be applied to. In particular, patches from Stephen Tweedie and Jeremy Fitzhardinge: http://lists.xen.org/archives/html/xen-devel/2009-05/msg00228.html and http://lists.xen.org/archives/html/xen-devel/2009-05/msg00538.html Thanks! Regards, Howell.

I am receiving a list of name collisions when I launch R as seen below. I'm new to R and any suggestion or help with how I can go about getting rid of these collisions would be greatly appreciated. % R R version 2.5.1 (2007-06-27) Copyright (C) 2007 The R Foundation for Statistical Computing ISBN 3-900051-07-0 R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to

Hallo Mailinglist:), i used xen 4.1 with xend xm a while. I compiled the unstable 4.2 today and most thinks run fine :). I have only one big problem, the network for my guestsystems. It don't want to work. Hopefully somebody can help me. In Xen 4.1 i only wrote the following line in my questconfig: vif = [ "bridge=eth0,script=vif-bridge" ] And everything works fine. This does not

There are significant components of the upstream 5.6 release which are stuck behind the CentOS 5.6 release process, but are now incorporated in EPEL 5 components. In particular, the "php53" package is now necessary for the "drupal6" EPEL components, due to the long out of date PHP 5.1 in the default upstream vendor's codebase. I see that some of these components are