thinice's questions

Take this wrapper around ssh_authorized_key for example:

define sshauthkeys::helper ($user,$ensure='present') {


        ssh_authorized_key { "puppet: ${name2} ${user}":
          ensure => $ensure,
          type => $ssh_keys["${name2}"]["type"],
          key => $ssh_keys["${name2}"]["key"],
          user => "${user}"
        }
}

Let's say I wanted to introduce support of the 'target' parameter for that resource type, I'd do something like:

define sshauthkeys::helper ($user,$ensure='present', $target='') {

The problem is, if I want to use the sensible default from puppet derived from $user 's homedir - and override it on fringe cases, I lose the benefit of the work done to set the default in all of the other circumstances.

Is there a way to optionally override the value without having to write two functions?

Better description of the issue:

define sshauthkeys::helper ($user,$ensure='present', $target='') {

    ssh_authorized_key { "puppet: ${name2} ${user}":
      // etc etc...
      target = $target 
      // ^--- Here, I'm forcing it to '' - how do I use the puppet 
      // built-in derivation, and only override optionally?
    }

}

I'm getting the ball rolling on puppet for my environment - and I'd like to have a conditional file resource based on whether or not the module itself contains a file based on a naming convention.

So visually, assume a module named 'mysql' and it's layout:

mysql/
    /files
        /etc/
            my.cnf
            my.hostname1.cnf
            my.hostname2.cnf
     /manifests
            init.pp
...

So I'd like the block to verify if the resource for the module exists or not, and take action accordingly, in pseudo-terms:

file { '/etc/my.cnf':

  if -f 'puppet:///mysql/etc/my.$hostname.cnf' {
      source => 'puppet:///mysql/etc/my.$hostname.cnf'
  }
  else {
      source => 'puppet:///mysql/etc/my.cnf'
  }
}

This way one wouldn't have to manage a csv file or the .pp file with a host specific case statement - is this possible?

I've got two Dell PE R710's -

• A has a single socket and 3 DIMMs in one bank
• B has both sockets and 6 (2 banks @ 3 DIMMs) filled

The output from "ipmitool sdr entity 8" confuses me - according to the OpenIPMI documentation these are supposed to represent DIMM slots.

Output from A (1 CPU, 3 DIMMS, 1 bank.):

~#: ipmitool sdr entity 8

Temp             | 0Ah | ok  |  8.1 | 27 degrees C
Temp             | 0Bh | ns  |  8.1 | Disabled
Temp             | 0Ch | ucr |  8.1 | 52 degrees C

Output from B (2 CPUs, 3 DIMMS in both banks, 6 total):

~#: ipmitool sdr entity 8

Temp             | 0Ah | ok  |  8.1 | 26 degrees C
Temp             | 0Bh | ok  |  8.1 | 25 degrees C
Temp             | 0Ch | ucr |  8.1 | 51 degrees C

Now, I'm starting to think this output isn't DIMMS themselves, but maybe a sensor for each bank and something else? (Otherwise, shouldn't I see 6 readings for the one with both banks active?)

The CPU's aren't near 50 deg C, so I doubt the significantly higher reading is due to proximity - Is anyone able to explain what I'm seeing?

Does the output from my ipmitool sdr entity 8 -v here on pastebin seem to hint at different sensors?

The sensor naming conventions are poor - seems like a dell thing.

Here is output from racadm racdump

I'm digging through the output of ipmitool sdr list on a Dell PE R710 - and I see there's a sensor reading named "Planar Temp" - which reads higher than the ambient temperature but lower than the CPU temps.

Both entities for "Ambient" and "Planar" are a part of the board; What is "Planar Temp" referring to in this context?

Apache doesn't let .htaccess use frills such as Location, Directory - without these, is it possible to match a url pattern and set php configuration settings (via php_value) in a .htaccess file?

A development server I'm responsible for (ext3 on raid 5 w/Debian Squeeze) froze up over the weekend and I was forced to reset it, as in unresponsive from KVM/physical keyboard access, no eth devices responding, etc. Not even the backup process ran (Figures, the one time I don't check for confirmation)

So after the reset, it turns out that every trace of disk IO activity that should have happened for a period of ~24H is completely gone. The log files have a big gap in the dates and times. As if the writes were never committed to disk, no processes seemed to have run.

Luckily it was a weekend and nothing of value would have been lost and I don't suspect a hack.

What can I do in post mortem to this event - to prevent it from ever happening again? I've seen this happen before on a completely different machine running FreeBSD.

I am rounding up the disk checking tools right now - but there must be more going on!

• Mount options: /dev/sda1 on / type ext3 (rw,errors=remount-ro)
• Kernel: Linux dev 2.6.32-5-686-bigmem
• Disk/Inodes: 13%/3%

I'm attempting to test the install procedure for libpam_ldapd on an Ubuntu/Debian Virtual machine.

I have the nscd / nslcd services off, and I'm watching the output from nslcd -d and /var/log/auth.log,

My filters / maps I've setup in nslcd.conf are working correctly, I'm only using ldap for passwords - meaning I only want to check the passwords for accounts that already exist on the system, thus I'm only using:

shadow files ldap in /etc/nsswitch.conf

The output from nslcd -d says the bind is working fine, but the auth log is stating:

sshd[]: pam_ldap(sshd:auth): username changed from rovangju to RovangJu
sshd[]: pam_unix(sshd:account): could not identify user (from getpwnam(RovangJu))
sshd[]: Failed password for rovangju from 127.0.0.1 port 44245 ssh2

The console that's attempting the SSH login does not receive any errors:

rovangju@vbox-u64:~$ ssh 0
rovangju@0's password: [enter correct password]
Connection closed by 127.0.0.1

It's apparent that the bind is using the cn/uid from the ldap property, which is a username with capital letters, however unix usernames are all lowercase. Does anyone know how to work around this?

The closest thing I've found for this problem is here: http://forums.opensuse.org/english/get-technical-help-here/install-boot-login/445925-pam_ldap-username-case-sensitivity-opensuse-11-2-a.html

Thanks in advance!

Edit: Another kicker is this: For some reason, I can trick the module by doing this:

rovangju@vbox-u64:~$ ssh 0
rovangju@0's password: [enter WRONG password]
Permission denied, please try again
rovangju@0's password: [enter CORRECT password]
[and bingo, I'm in]