I had the same problem. I couldn’t figure out how to get rtmux.pl to
read in config.pm properly. In the end, I added all of the variable
settings from config.pm to rtmux.pl where it tried to read config.pm,
and it worked out fine.
BTW, I’m running Redhat Linux 6.2, rt 1.0.4, apache 1.3.11, perl 5.6.0, and
mysql 3.23.24.
sounds like suidrt or webrt.cgi has lost its suidness.
try running "make fixperms"On Thu, Sep 28, 2000 at 08:24:40AM +1200, Dan Shauver wrote:
I had the same problem. I couldn’t figure out how to get rtmux.pl to
read in config.pm properly. In the end, I added all of the variable
settings from config.pm to rtmux.pl where it tried to read config.pm,
and it worked out fine.
BTW, I’m running Redhat Linux 6.2, rt 1.0.4, apache 1.3.11, perl 5.6.0, and
mysql 3.23.24.
jesse reed vincent — root@eruditorum.org — jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
. . . when not in doubt, get in doubt. – Old Discordian Proveb
I swore that ‘require’ or ‘use’ allowed you to specify a version
number after the module name but I might be confusing that with
‘use 5.005;’ to specify the minumum allowable perl version.
[insert sound of me rummaging through my perl books here]
Ha! I knew it! p305 of Programming Perl (3d edition) explains it all.
The above code snippet returns 2.46 on my machine; let’s see
what happens when I change the code to:
CGI version 2.48 required–this is only version 2.46 at -e line 1.
BEGIN failed–compilation aborted at -e line 1.
t might also be helpful if the installation scripts check that
$CGI::VERSION is greater than some tested minimum version
(2.32?) and spoot out the appropriate warning.
Sorry for not including a patch; it should be Yet Another 5 Minute
Fix That I Can Never Find 5 Minutes For (having been there
myself). When I get back to the office next week I’ll try to
contribute something more useful along these lines.
hth,
– BobOn 28 Sep 00, at 13:29, Ralph Angenendt wrote:
nod we have a prereqs script for RT2. I’m trying not to spend too much time with RT1 right now.
Though I have a couple patches to add and then roll 1.0.5…On Thu, Sep 28, 2000 at 11:23:49PM -0500, arclight@jump.net wrote:
Hi,
Take a look at:
perl -e ‘use CGI; print $CGI::VERSION, “\n”;’
I swore that ‘require’ or ‘use’ allowed you to specify a version
number after the module name but I might be confusing that with
‘use 5.005;’ to specify the minumum allowable perl version.
[insert sound of me rummaging through my perl books here]
Ha! I knew it! p305 of Programming Perl (3d edition) explains it all.
The above code snippet returns 2.46 on my machine; let’s see
what happens when I change the code to:
CGI version 2.48 required–this is only version 2.46 at -e line 1.
BEGIN failed–compilation aborted at -e line 1.
t might also be helpful if the installation scripts check that
$CGI::VERSION is greater than some tested minimum version
(2.32?) and spoot out the appropriate warning.
Sorry for not including a patch; it should be Yet Another 5 Minute
Fix That I Can Never Find 5 Minutes For (having been there
myself). When I get back to the office next week I’ll try to
contribute something more useful along these lines.
jesse reed vincent — root@eruditorum.org — jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
A REAL sysadmin challenge is “resurrect five dead mailserver while so ripped
to the gills on mdma that you can’t focus on any given line of text for more
than 10 seconds continuously.”
-Nathan Mehl