ppr-list-digest volume 5, number 45, message 8

Note: please don't spam any of the e-mail addresses which you see here. Follow this link if you want some addresses to misuse.


From: Kenneth Tindle <ktindle@uky.edu>
Date: Mon, 04 Aug 2003 16:54:00 -0400
Subject: PPR: ppop puzzle deepens

OK, so I can't communicate with ppop via the Web admin system.
So, I did:

rpm -q perl
perl-5.8.0-88

rpm -V perl
comes back with nothing (it's happy.)

So my Perl installation is not obviously broken.  So, I wrote this
script:

- ----
#!/usr/bin/perl -wT

delete $ENV{PATH};
delete $ENV{BASH_ENV};
delete $ENV{CD_PATH};
delete $ENV{IFS};

use FileHandle;
use IPC::Open2;

my @COMMAND = ("/usr/lib/ppr/bin/ppop");
push(@COMMAND, "-M");
print @COMMAND, "\n";
($rdr, $wtr) = (FileHandle->new, FileHandle->new);
my $pid = open2($rdr, $wtr, @COMMAND);
my $got = <$rdr>;
print $got, "\n";
- ----
And this yields:

/usr/lib/ppr/bin/ppop-M
*READY	1.51

as expected!

Note that this is running as root.

It would seem that PPOP.pm, when run as pprwww, will launch ppop
but not communicate with it.  It will work when run as root.

These permissions on ppop:

- -rws--s--x   ppr   ppr

must be wrong.  David, on your RH9 box that is happily running
the www admin system, could you take a peek at your permissions?
Along with the uid/gid?
Is anybody running the www admin system using the released 1.51
tarball, and it's working OK for you?

Sigh.