I take your point about /etc/genders. I'll take a look to see if there's an easy fix, and in any case, I'll forward it upstream. For .WCOLL, I believe that the program only checks for the file if you have the WCOLL environment variable set. Can you confirm that is the case?
On Feb 12, 2008 9:22 PM, Joel Becker <[EMAIL PROTECTED]> wrote: > > > Package: pdsh > > Version: 2.10-3 > > Severity: normal > > > > The pdsh program provides multiple ways to specify target hosts. You > > can use a file .WCOLL in your home directory. You can use the genders > > database. You can use netgroups. You can even specify specific hosts > > on the command line with the -w option. > > > > The problem is that pdsh *REQUIRES* the .WCOLL file *AND* the > > /etc/genders file, even if neither is being used. I run: > > > > $ pdsh -w host1,host2 hostname > > > > I expect to have the "hostname" command run on host1,host2, as pdsh has > > all the information it needs to do so (and this works on IBM's dsh, my > > dsh, and even the dsh included with Debian). Instead, I get the > > following error: > > > > $ pdsh -w host1,host2 hostname > > [EMAIL PROTECTED]: /home/jlbec/.WCOLL: No such file or directory > > > > .WCOLL is not needed, but there is no option to ignore this. So I > > touch(1) $HOME/.WCOLL - not a fix, a workaround. I get the following > > error: > > > > $ touch ~/.WCOLL > > $ pdsh -w host1,host2 hostname > > [EMAIL PROTECTED]: Unable to open genders file: error opening genders > > file > > > > Again, I don't need genders to function. But pdsh refuses to run > > without it. Let's try touch(1) again - this time I need _root_ > > permissions: > > > > $ su - -c 'touch /etc/genders' > > Password: > > $ pdsh -w host1,host2 hostname > > [EMAIL PROTECTED]: Unable to open genders file: genders file parse error > > > > Heavens! An empty configuration isn't even valid! Next we'll try > > garbage: > > > > $ su - -c 'echo foo > /etc/genders' > > Password: > > $ pdsh -w host1,host2 hostname > > host1: host1.mydomain.com > > host2: host2.mydomain.com > > > > This is silly. pdsh knows from the -w option what it has to do. It > > should not require empty configuration files that are irrelevant - let > > alone empty files I require _root_ permission to create! > > > > -- System Information: > > Debian Release: lenny/sid > > APT prefers unstable > > APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') > > Architecture: i386 (i686) > > > > Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > > Shell: /bin/sh linked to /bin/bash > > > > Versions of packages pdsh depends on: > > ii debconf [debconf-2.0] 1.5.19 Debian configuration > > management sy > > ii genders 1.6-1-1 cluster configuration > > management d > > ii libc6 2.7-6 GNU C Library: Shared > > libraries > > ii libgenders0 1.6-1-1 C library for parsing and > > querying > > ii openssh-client [rsh-client] 1:4.7p1-3 secure shell client, an > > rlogin/rsh > > ii perl 5.8.8-12 Larry Wall's Practical > > Extraction > > ii rsh-client 0.17-14 rsh clients > > ii ssh 1:4.7p1-3 secure shell client and > > server (me > > > > pdsh recommends no packages. > > > > -- debconf information: > > * pdsh/setuidroot: false > > > > > > >
