similar to: dovecot ldap search result ordering?

Hi I''m been trying to install an xvm instance on a remote system, but I keep running into variations on ''unable to open display'' I''ve tried to use ssh -X but I''ve not been able to get it to forward when su''d to root. 1) ssh -X -l xadmin virtbox running cload etc works fine. 2a i. su - ii. cp .Xauthority ~xadmin/.Xauthority iii. setenv

Hi, I had to rearrange the user accounts on my iMac (10.6.8) and need to re-instal WINE from the new admin account since the original one got mucked up (for one thing, the .wine directory got deleted which is in user space). It's objecting to the activation of python27: ---> Activating python27 @2.7.2_0+universal Error: Target org.macports.activate returned: Image error:

G''day my module''s init.pp: class mailaliases { if ($skip_mailaliases != "true") { mailalias { "root": # ensure => absent, ensure => present, target => "/etc/aliases", recipient =>

HI, All our unix boxes under puppet are configured with the ''mailalias'' resource type as in : mailalias { "root": recipient => "linuxroot@fqdn", ensure => present } The majority of those boxes however don''t have /etc/aliases served out by puppet, rather, they simply have the installed default /etc/aliases locally.

Hi all, hoping someone may have encountered a problem similar to this before: On my customer''s EC2 based infrastructure, we have implemented the nodeless, truth driven module outlined by Jordan Sissel here http://www.semicomplete.com/blog/geekery/puppet-nodeless-configuration. It''s quite an effective model, especially in the realm of EC2... we still have a puppetmaster

Over the years many shops have come to start running puppet via cron to address memory leaks in earlier versions of Ruby, but the official position was that puppet was meant to be run as a continually running service. I am wondering if the official position has changed. On one hand many if not all of the early Ruby issues have been fixed, on the other, the addition of mcollective into the mix as

Hey guys, i just wanne report that our debian squeeze xen machines are also influenced by this bug, and we tried the workaround with the debug option by building our own linux-image-2.6.32-5-xen-amd64_2.6.32-31_amd64.deb but this isnt a workaround really, we tested it on an 40 vmachines dom0 and it just dont work, of course the lvm works but the machine is slow as hell and runs into several