from:"Eric"

:) I think that makes sense. It was created in the child.  It seemed to be
fixed when I made the connection global. When I tried the connection in the
child again it might well have been a lucky transpireing of events that let
the child stay alive long enough for the query to get completed. So I should
keep it global I think. 

Thanks,

Eric 

At 04:24 PM 9/16/03 +0100, Stephen Hardisty wrote:
>Hi,
>is the database connection created in the child or before it?
>If it's created inside the child then it'll die ungracefully when the child
>dies, so put something nice and fluffy to close it before the exit.
>Otherwise, I don't know I'm afraid.
>
>-Original Message-
>From: Eric Frazier [mailto:[EMAIL PROTECTED]
>Sent: 16 September 2003 12:57
>To: Stephen Hardisty
>Cc: [EMAIL PROTECTED]
>Subject: RE: mod_perl v2 Forking
>
>
>Hi,
>
>Doing this "works" for me. But I am ending up with some errors that I didn't
>have before. Of course my bosses would get mad if I posted all of the code
>involed, but basicly a database connection that was working fine is now
>returning "mysql server has gone away", meaning that the connection got
>killed. What is weird/scary, is that if I change your $SIG{CHLD} = 'IGNORE';
>back to the handler I was using, the database error goes away, but I am back
>were I was. Fun huh? :) 
>
>Thanks,
>
>Eric 
>
>At 03:57 PM 9/16/03 +0100, Stephen Hardisty wrote:
>>Hi,
>>I had a problem with 5.8.1 and forking in that I was either getting zombies
>using the 5.6 examples or the parent was dying, depending on which example
>was used. The way round I found was to:
>>
>># ignore the child, good rule for life
>>$SIG{CHLD} = 'IGNORE';
>>
>># then sort out the socket
>>my $server = new IO::Socket::INET(LocalPort => $port,
>>  Type => SOCK_STREAM,
>>  Proto => "tcp",
>>  Listen => 5)
>>  or die "some error";
>>
>># wait for a connection
>>while(my $client = $server->accept())
>>{
>>  my $pid = fork;
>>  die "Error. Fork: $!\n" unless defined $pid;
>>
>>  if($pid == 0)
>>  {
>>  # all your child code here
>>
>>  # when it's done, kill the child:
>>  exit(0);
>>  }
>>}
>>
>>This seemes reasonably stable. If anybody has a better way, then I'm all ears.
>>
>>Cheers!
>>
>>-Original Message-
>>From: Eric Frazier [mailto:[EMAIL PROTECTED]
>>Sent: 16 September 2003 12:24
>>To: [EMAIL PROTECTED]
>>Cc: [EMAIL PROTECTED]
>>Subject: Re: mod_perl v2 Forking
>>
>>
>>Hi,
>>
>>I guess this is off topic for this list, since I would be doing this no
>>matter if I was running CGI or mod_perl or whatever. I am pretty desparate
>>to get this working, and if anyone wants to earn some cash helping me fix
>>things PLEASE call me at 250 655-9513. 
>>
>>I have been trying to accomplish the same thing as Cameron, but with the
>>detaching stuff it seemed a lot easier to make a server with IO::Select and
>>not actually start the server from mod_perl. The end result hopefully will
>>be a web user being able to start some things that take time, but not screw
>>things up by interrupting them. 
>>
>>But then I found I was using 5.8.. Thanks to a guy on comp.lang.perl.misc I
>>know that there is a change in how signals are handled, they call it
>>deferred signal handling because Perl now is suppose to wait until the
>>Interpeter is in a safe state. As I understand it this might avoid some
>>things like core dumps or other errors related to dieing while trying to do
>>something besides dieing. 
>>
>>The thing is somehow this ends up killing off my parent process, just like
>>in this post:
>>
>>http://www.mail-archive.com/[EMAIL PROTECTED]/msg43989.html
>>
>>So this is happening to me as well, however the guy in the above example had
>>his problem solved by using Errno and looking for EINTR if that error is
>>raised then catch it and move on, 
>>
>>I did get one maybe helpfull thing from my log:
>>
>>Erro was  %! 
>>./franken_socket.pl 8607: got - CHLD
>> at Tue Sep 16 02:17:42 2003
>>I got forked
>>./franken_socket.pl 8599: begat 8607 at Tue Sep 16 02:17:40 2003
>>begat 8607
>>./franken_socket.pl 8599: got - CHLD
>> at Tue Sep 16 02:17:54 2003
>>./franken_socket.pl 8599: main 860

RE: mod_perl v2 Forking

Hi,

Well, I am not sure if this is going to be the best solution long term, but
it works!

 while ( <$connection> ){

my $return_value = undef;

if(/quit|exit/i){ last;}
elsif (/closeme/i ) {$connection->close(); }
elsif (/date|time/i){ printf $connection "%s\n", scalar
localtime; exit(0);  }

that did call to a sub, and then connected to a database. I am wondering if
that connection object is better off being global. I changed the connect to
be global, restarted and did a test and it worked fine! I was all ready to
post back to here with the good news, when just to double check I went back
and made the db connect in the local sub like before. And it still worked?!
So it seems like I might be in better shape for now, but I might have some
long term problems with DB connections dieing, most likely related to this
child handling. I have to think that becase the query I am doing is VERY
well tested and never causes an issue. 

Thanks tremedously for everyone's help so far, I at the very least have some
directions to go in now.

I still would very much like to learn what the correct, put it in the book
solution should be.. 


Eric 




At 03:57 PM 9/16/03 +0100, Stephen Hardisty wrote:
>Hi,
>I had a problem with 5.8.1 and forking in that I was either getting zombies
using the 5.6 examples or the parent was dying, depending on which example
was used. The way round I found was to:
>
># ignore the child, good rule for life
>$SIG{CHLD} = 'IGNORE';
>
># then sort out the socket
>my $server = new IO::Socket::INET(LocalPort => $port,
>  Type => SOCK_STREAM,
>  Proto => "tcp",
>  Listen => 5)
>   or die "some error";
>
># wait for a connection
>while(my $client = $server->accept())
>{
>   my $pid = fork;
>   die "Error. Fork: $!\n" unless defined $pid;
>
>   if($pid == 0)
>   {
>   # all your child code here
>
>   # when it's done, kill the child:
>   exit(0);
>   }
>}
>
>This seemes reasonably stable. If anybody has a better way, then I'm all ears.
>
>Cheers!
>
>-Original Message-
>From: Eric Frazier [mailto:[EMAIL PROTECTED]
>Sent: 16 September 2003 12:24
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: Re: mod_perl v2 Forking
>
>
>Hi,
>
>I guess this is off topic for this list, since I would be doing this no
>matter if I was running CGI or mod_perl or whatever. I am pretty desparate
>to get this working, and if anyone wants to earn some cash helping me fix
>things PLEASE call me at 250 655-9513. 
>
>I have been trying to accomplish the same thing as Cameron, but with the
>detaching stuff it seemed a lot easier to make a server with IO::Select and
>not actually start the server from mod_perl. The end result hopefully will
>be a web user being able to start some things that take time, but not screw
>things up by interrupting them. 
>
>But then I found I was using 5.8.. Thanks to a guy on comp.lang.perl.misc I
>know that there is a change in how signals are handled, they call it
>deferred signal handling because Perl now is suppose to wait until the
>Interpeter is in a safe state. As I understand it this might avoid some
>things like core dumps or other errors related to dieing while trying to do
>something besides dieing. 
>
>The thing is somehow this ends up killing off my parent process, just like
>in this post:
>
>http://www.mail-archive.com/[EMAIL PROTECTED]/msg43989.html
>
>So this is happening to me as well, however the guy in the above example had
>his problem solved by using Errno and looking for EINTR if that error is
>raised then catch it and move on, 
>
>I did get one maybe helpfull thing from my log:
>
>Erro was  %! 
>./franken_socket.pl 8607: got - CHLD
> at Tue Sep 16 02:17:42 2003
>I got forked
>./franken_socket.pl 8599: begat 8607 at Tue Sep 16 02:17:40 2003
>begat 8607
>./franken_socket.pl 8599: got - CHLD
> at Tue Sep 16 02:17:54 2003
>./franken_socket.pl 8599: main 8607 -- reaped 1 at Tue Sep 16 02:17:54 2003
>reaped 1Erro was No child processes %! 
>
>So it looks like the parent got killed on that  error "No child process" 
>This code works just fine on 5.6 since it is about 150% from examples :) 
>The above is the result of connecting, doing a "who", and doing "dienow" to
>test the alarm. 
>
>I also found this: 
>
>http://archive.develooper.com/[EMAIL PROTECTED]/msg03022.html
>
>Which totaly describ

RE: mod_perl v2 Forking

Hi,

Doing this "works" for me. But I am ending up with some errors that I didn't
have before. Of course my bosses would get mad if I posted all of the code
involed, but basicly a database connection that was working fine is now
returning "mysql server has gone away", meaning that the connection got
killed. What is weird/scary, is that if I change your $SIG{CHLD} = 'IGNORE';
back to the handler I was using, the database error goes away, but I am back
were I was. Fun huh? :) 

Thanks,

Eric 

At 03:57 PM 9/16/03 +0100, Stephen Hardisty wrote:
>Hi,
>I had a problem with 5.8.1 and forking in that I was either getting zombies
using the 5.6 examples or the parent was dying, depending on which example
was used. The way round I found was to:
>
># ignore the child, good rule for life
>$SIG{CHLD} = 'IGNORE';
>
># then sort out the socket
>my $server = new IO::Socket::INET(LocalPort => $port,
>  Type => SOCK_STREAM,
>  Proto => "tcp",
>  Listen => 5)
>   or die "some error";
>
># wait for a connection
>while(my $client = $server->accept())
>{
>   my $pid = fork;
>   die "Error. Fork: $!\n" unless defined $pid;
>
>   if($pid == 0)
>   {
>   # all your child code here
>
>   # when it's done, kill the child:
>   exit(0);
>   }
>}
>
>This seemes reasonably stable. If anybody has a better way, then I'm all ears.
>
>Cheers!
>
>-Original Message-
>From: Eric Frazier [mailto:[EMAIL PROTECTED]
>Sent: 16 September 2003 12:24
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: Re: mod_perl v2 Forking
>
>
>Hi,
>
>I guess this is off topic for this list, since I would be doing this no
>matter if I was running CGI or mod_perl or whatever. I am pretty desparate
>to get this working, and if anyone wants to earn some cash helping me fix
>things PLEASE call me at 250 655-9513. 
>
>I have been trying to accomplish the same thing as Cameron, but with the
>detaching stuff it seemed a lot easier to make a server with IO::Select and
>not actually start the server from mod_perl. The end result hopefully will
>be a web user being able to start some things that take time, but not screw
>things up by interrupting them. 
>
>But then I found I was using 5.8.. Thanks to a guy on comp.lang.perl.misc I
>know that there is a change in how signals are handled, they call it
>deferred signal handling because Perl now is suppose to wait until the
>Interpeter is in a safe state. As I understand it this might avoid some
>things like core dumps or other errors related to dieing while trying to do
>something besides dieing. 
>
>The thing is somehow this ends up killing off my parent process, just like
>in this post:
>
>http://www.mail-archive.com/[EMAIL PROTECTED]/msg43989.html
>
>So this is happening to me as well, however the guy in the above example had
>his problem solved by using Errno and looking for EINTR if that error is
>raised then catch it and move on, 
>
>I did get one maybe helpfull thing from my log:
>
>Erro was  %! 
>./franken_socket.pl 8607: got - CHLD
> at Tue Sep 16 02:17:42 2003
>I got forked
>./franken_socket.pl 8599: begat 8607 at Tue Sep 16 02:17:40 2003
>begat 8607
>./franken_socket.pl 8599: got - CHLD
> at Tue Sep 16 02:17:54 2003
>./franken_socket.pl 8599: main 8607 -- reaped 1 at Tue Sep 16 02:17:54 2003
>reaped 1Erro was No child processes %! 
>
>So it looks like the parent got killed on that  error "No child process" 
>This code works just fine on 5.6 since it is about 150% from examples :) 
>The above is the result of connecting, doing a "who", and doing "dienow" to
>test the alarm. 
>
>I also found this: 
>
>http://archive.develooper.com/[EMAIL PROTECTED]/msg03022.html
>
>Which totaly describes my problem as well, but shows it happening with perl
>5.8.1.. 
>
>
>>I'd imagine that your accept() isn't being restarted.  How does it work
>>if you change the loop to look like this?
>
>>use Errno;
>
>>while (1) {
>>  my $client = $server->accept or do {
>>   next if $!{EINTR};
>>last;
>>  };
>>  spawn(\&function, "whatever");
>>}
>
>#!/usr/bin/perl -w
>
>## new frankenstein!
>
>  use strict;
>  use POSIX ();
>  use POSIX 'WNOHANG';
>  use Errno;
>  use IO::Socket;
>  use FindBin ();
>  use File::Basename ();
>  use File::Spec::Functions;
>  use Net::hostent;
>

Re: mod_perl v2 Forking

Hi,

That sound like one way to go, I want to be very careful with something like
this. You speak as if restoring 5.6 behaviour is the best or only way to go.
Do you see any other alternatives? 

Thanks,

Eric 

At 04:57 PM 9/16/03 +0200, Rafael Garcia-Suarez wrote:
>Eric Frazier wrote:
>...
>> But then I found I was using 5.8.. Thanks to a guy on comp.lang.perl.misc I
>> know that there is a change in how signals are handled, they call it
>> deferred signal handling because Perl now is suppose to wait until the
>> Interpeter is in a safe state. As I understand it this might avoid some
>> things like core dumps or other errors related to dieing while trying to do
>> something besides dieing. 
>
>Mostly, yes. Look at the perldelta manpage that is distributed with perl
>5.8.0, section "Safe Signals".

I did read that, it seems kind of misleading. The 5.8 IPC doc was more
helpful, but I still didn't get a clear idea how to handle this and the
examples are not updated yet.


>
>If you want to restore the 5.6-ish "unsafe" signal handling, this is not
>possible with 5.8.0 :(. But, as it has been acknowledged that this unsafe
>behaviour is desirable in some cases, it will be possible with perl
>5.8.1.
>
>You can grab a 5.8.1 release candidate 4 from CPAN :
>http://search.cpan.org/~jhi/
>(RC5 should be out in a few days)
>and see with it if using unsafe signal handlers solves your problem.
>You can enable them with the PERL_SIGNALS environment variable.
>Here's the relevant part of the perlrun manpage that comes with perl
>5.8.1 RC4 :
>
>=item PERL_SIGNALS
>
>In Perls 5.8.1 and later.  If set to C the pre-Perl-5.8.0
>signals behaviour (immediate but unsafe) is restored.  If set to
>C the safe (or deferred) signals are used.
>See L.
>
>HTH.
>

(250) 655 - 9513 (PST Time Zone)

"Inquiry is fatal to certainty." -- Will Durant

Re: mod_perl v2 Forking

Hi,

I guess this is off topic for this list, since I would be doing this no
matter if I was running CGI or mod_perl or whatever. I am pretty desparate
to get this working, and if anyone wants to earn some cash helping me fix
things PLEASE call me at 250 655-9513. 

I have been trying to accomplish the same thing as Cameron, but with the
detaching stuff it seemed a lot easier to make a server with IO::Select and
not actually start the server from mod_perl. The end result hopefully will
be a web user being able to start some things that take time, but not screw
things up by interrupting them. 

But then I found I was using 5.8.. Thanks to a guy on comp.lang.perl.misc I
know that there is a change in how signals are handled, they call it
deferred signal handling because Perl now is suppose to wait until the
Interpeter is in a safe state. As I understand it this might avoid some
things like core dumps or other errors related to dieing while trying to do
something besides dieing. 

The thing is somehow this ends up killing off my parent process, just like
in this post:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg43989.html

So this is happening to me as well, however the guy in the above example had
his problem solved by using Errno and looking for EINTR if that error is
raised then catch it and move on, 

I did get one maybe helpfull thing from my log:

Erro was  %! 
./franken_socket.pl 8607: got - CHLD
 at Tue Sep 16 02:17:42 2003
I got forked
./franken_socket.pl 8599: begat 8607 at Tue Sep 16 02:17:40 2003
begat 8607
./franken_socket.pl 8599: got - CHLD
 at Tue Sep 16 02:17:54 2003
./franken_socket.pl 8599: main 8607 -- reaped 1 at Tue Sep 16 02:17:54 2003
reaped 1Erro was No child processes %! 

So it looks like the parent got killed on that  error "No child process" 
This code works just fine on 5.6 since it is about 150% from examples :) 
The above is the result of connecting, doing a "who", and doing "dienow" to
test the alarm. 

I also found this: 

http://archive.develooper.com/[EMAIL PROTECTED]/msg03022.html

Which totaly describes my problem as well, but shows it happening with perl
5.8.1.. 


>I'd imagine that your accept() isn't being restarted.  How does it work
>if you change the loop to look like this?

>use Errno;

>while (1) {
>  my $client = $server->accept or do {
>   next if $!{EINTR};
>last;
>  };
>  spawn(\&function, "whatever");
>}

#!/usr/bin/perl -w

## new frankenstein!

  use strict;
  use POSIX ();
  use POSIX 'WNOHANG';
  use Errno;
  use IO::Socket;
  use FindBin ();
  use File::Basename ();
  use File::Spec::Functions;
  use Net::hostent;
  use Carp;
 

  $|=1;
  my $pid;

open (DIED, ">>/var/log/daemon_log") or warn "$!";
sub logmsg { print DIED "$0 $$: @_ at ", scalar localtime, "\n" }

my $listen_socket = IO::Socket::INET->new(LocalPort => 1081,
LocalAddr => '127.0.0.1',
Proto => 'tcp',
Listen=> SOMAXCONN,
Reuse => 1 )
or die "can make a tcp server on port 1080 $!";


  # make the daemon cross-platform, so exec always calls the script
  # itself with the right path, no matter how the script was invoked.
  my $script = File::Basename::basename($0);
  my $SELF = catfile $FindBin::Bin, $script;
  # POSIX unmasks the sigprocmask properly
  my $sigset = POSIX::SigSet->new();
  my $action = POSIX::SigAction->new('sigHUP_handler',
 $sigset,
 &POSIX::SA_NODEFER);
  my $action_alrm = POSIX::SigAction->new('sigALRM_handler',
 $sigset,
 &POSIX::SA_NODEFER);


  POSIX::sigaction(&POSIX::SIGHUP, $action);
 POSIX::sigaction(&POSIX::SIGALRM, $action_alrm);

  sub sigHUP_handler {
  print "got SIGHUP\n";
  exec($SELF, @ARGV) or die "Couldn't restart: $!\n";
  }
  sub sigALRM_handler {
  print "got ALARM timeout\n";

  }

  $SIG{CHLD} = \&REAPER_NEW;

  sub REAPER {
$SIG{CHLD} = \&REAPER;  # loathe sysV
my $waitedpid = wait;
logmsg "reaped $waitedpid" . ($? ? " with exit $?" : '');
}

sub REAPER_NEW {
logmsg "got - @_\n";
my $wpid = undef;
while ($wpid = waitpid(-1,WNOHANG)>0) {

logmsg "main $pid -- reaped $wpid" . ($? ? " with exit $?" : '')
;
print DIED "reaped $wpid" . ($? ? " with exit $?" : '');

}
}


   print "PID: $$\n";
   print "ARGV: @ARGV\n";
   print "[Server $0 accepting clients]\n";

#while (my $connection = $listen_socket->accept()) {
while (1) {
  my $connection = $listen_socket->accept() or do {
next if $!{EINTR};
last;
  };

print DIED "Erro was $! %! \n";
$connection->autoflush(1); ## missing seemed to cause client problem, but
not telnet

if (

Re: Apache::Session permissions problem

2003-09-15 Thread Eric Schwartz

On Saturday, Sep 13, 2003, at 09:22 America/Denver, Perrin Harkins 
wrote:
I found a pretty useful article at
http://www.linuxjournal.com/article.php?sid=4143 on how to use
Apache::Session with Mason.
I'm afraid that is not a very good article.  It's out of date, and 
shows
poor error handling.  If you want to use sessions with Mason, you 
should
be using the session handler that Mason provides.  That is available on
CPAN and is supported on the Mason list.
Beggars can't be choosers, and all that, but would you mind telling me 
what handler you're talking about?  I looked around for session 
handling and Mason, and that article was the best one I found in terms 
of explaining how it worked and how to use it.

Apache::Session::DBI (which is what the article refers to) is ancient 
and
should not be used.
How can I know this?  The documentation for Apache::Session::DBIStore 
(which A::S::DBI refers to) doesn't say anything about being obsolete 
or deprecated.  Is there an archive of received wisdom somewhere I 
should be checking to validate articles like the one I found?

You shouldn't use the IPC locking in Apache::Session.  You didn't 
mention
which database you're using, but most of them have alternative ways of
doing locking.  In my opinion, the locking approach taken in
Apache::Session is not a good one for the average web site and you 
should
simply turn it off by using the NullLocker.
How?  I never asked for IPC locking; it somehow snuck in.  It's not 
particularly obvious from the documentation I can find that it's going 
to be used, or how to select alternative methods.  I installed 
Apache::Session from CPAN, and the docs refer to PosixFileLocker 
SysVSemaphoreLocker and NullLocker, but no perldocs for those modules 
are on my system.  I'm honestly trying to figure out how I can draw 
those conclusions for myself, so I'm not stuck asking this list about 
them.

Suggestions are more than welcome; I'm not quite sure how
Session::SysVSempaphoreLocker got involved in the first place, since I
don't explicitly reference it.
Apache::Session::DBI uses it for locking.
'perldoc Apache::Session::DBI' says it uses A::S::PosixFileLocker, not 
A::S::SysVSemaphoreLocker.  Are the docs wrong, or the code?

-=Eric

Apache::Session permissions problem

2003-09-12 Thread Eric Schwartz

I found a pretty useful article at 
http://www.linuxjournal.com/article.php?sid=4143 on how to use 
Apache::Session with Mason.  I followed the article, more or less, and 
ended up with this bit of code in my handler.pl to tie() my $session 
variable to an Apache::Session class:

  eval {
tie %HTML::Mason::Commands::session, 'Apache::Session::DBI',
  ($cookies{$session_cookie_name} ? 
$cookies{$session_cookie_name}->value() : undef),
{
 DataSource => $dbsource,
 UserName => $dbuser,
 Password => $dbpass
};
  };

All the database variables are correct; I use them elsewhere with no 
problem.  The problem is that the session seems to be intermittent-- 
some pages seem to recognize it, others don't.  This smelled a lot like 
a problem where the session was getting set in one Apache instance and 
not others, so I wondered if the session was getting stored in the 
database correctly; after the previous eval, all I ever get in $@ is:

Permission denied at 
/Library/Perl/Apache/Session/SysVSemaphoreLocker.pm line 46.

Which seems to indicate it isn't.  I STFW, and found several people who 
seem to have had the same problem I have, but the solutions proffered 
involve ipcs and ipcrm, which don't exist on my Mac OS X 10.2.6 system. 
 Suggestions are more than welcome; I'm not quite sure how 
Session::SysVSempaphoreLocker got involved in the first place, since I 
don't explicitly reference it.

Mightily confused,

-=Eric

Re: Apache::AuthCookie causing strange "Use of uninitialized value."

2003-09-12 Thread Per Eric Rosén

Thanks for your response!

> You have to subclass Apache::AuthCookie. This should be something like:
> PerlFixupHandler Your::Sublass->recognize_user

Well, I do. I just pasted the wrong text (from the 2002 mail).
The actual configuration snippet is:


AuthType TAS::Cookie
AuthName TAS
PerlFixupHandler TAS::Cookie->recognize_user


Another observation: It does only appear when no cookie is received.
When users are logged in, everything is fine. And, yes, I checked
recognize_user and put in a defined() around the cookie check. No result.
Even a bad cookie (manually deleting the session) makes it quiet.

/Per Eric
--
^): Per Eric Rosén http://rosnix.nu/~per/
/   [EMAIL PROTECTED]  GPG 7A7A BD68 ADC0 01E1 F560 79FD 33D1 1EC3 1EBB 7311

Apache::AuthCookie causing strange-"Use of uninitialized value."

2003-09-12 Thread Per Eric Rosén

I use Apache::AuthCookie 3.04, which seems to be the latest version, under
Apache/1.3.26 Ben-SSL/1.48 (Unix) Debian GNU/Linux PHP/4.1.2 mod_perl/1.26.

When I use "PerlFixupHandler Apache::AuthCookie->recognize_user", Apache
writes "Use of uninitialized value." in errorlog for each request and
subrequest. I have tried editing AuthCookie.pm, checking everything with
defined(), even substituting recognize_user with a stub function.

Still it is there. I am not sure it comes from perl, because perl use to
say "at line X" too. But from what else?

This has been up before, but no one answered it then:
http://www.jsw4.net/info/list-archives/mod_perl/02-08/msg00591.html

/Per Eric
--
^): Per Eric Rosén http://rosnix.nu/~per/
/   [EMAIL PROTECTED]  GPG 7A7A BD68 ADC0 01E1 F560 79FD 33D1 1EC3 1EBB 7311

Re: Possible Apache::AuthenSmb Mod?

2003-09-10 Thread Shannon Eric Peevey

Peter Hartzler wrote:

Hello,

We're looking into using your Apache::AuthenSmb module to allow us to
migrate our intranet to GNU/Linux/Apache.  One issue we have is that we
have two NT domains.  I have a couple of different ideas for how to modify
the code to allow this scenario, and am wondering if you have any thoughts
on this, or would be interested in a patch, or have a patch, or this is
already possible and somehow I've missed it...
There are a couple of obvious considerations, such as the possibility of 
userid duplication in the two domains (we don't do that), the need to not 
break existing/legacy configurations, and perhaps the desirability of 
passing the user's domain to the script (not sure about that one).

Anyhow, thanks for the very useful code, and do feel welcome to jump in if 
anything moves you!

Best Regards,

Pete.

 

Hi!

I think that Apache-AuthenNTLM may fit the bill for you.  Check it out at:

http://search.cpan.org/author/SPEEVES/Apache-AuthenNTLM-2.04/AuthenNTLM.pm

You are able to create mappings for more than one domain.

Also, please include the modperl mailing list in your replies.  (This 
email may have information that will help others in the future :) )

thanks,
speeves
cws

Re: apache2, mod_perl: problem with CGI

2003-09-06 Thread Shannon Eric Peevey

Stas Bekman wrote:

speeves wrote:

Stas Bekman wrote:

Thanks that did it.

Great.

It would be nice though if the minimum rev level of the CGI.pm
could be
mentioned in the doc.
Or maybe it is there somewhere and I skimmed over it.

It's a a CGI.pm problem, really. We can't go and support all
possible modules that may or may not run under mod_perl 2.0. However
we do have this section:
http://perl.apache.org/products/apache-modules.html#Porting_CPAN_modules_to_mod_perl_2_0_Status

We probably should specify the version number of each of these
modules. Can somebody please lookup those modules and send me a
patch with the version number which starts to support mod_perl 2.0?

No need for Apache::Peek, CGI and CGI::Cookie since I know these
versions already.

I'm CC'ing Shannon, since he has ported most of the auth modules.

Sorry, I wasn't following the thread, so don't know what the patch is
for. :( But, here is a listing of the version numbers for the auth
mods that are stable, and work with mod_perl2:

Apache-AuthenNIS-0.11
Apache-AuthenNTLM-2.04
Apache-AuthenPasswd-0.12
Apache-AuthenSmb-0.70
Apache-AuthExpire-0.38
Apache-AuthNetLDAP-0.25
Apache-AuthPerLDAP-2.01
Apache-AuthzNetLDAP-0.07
Apache-AuthzNIS-0.11
Apache-AuthzPasswd-0.11

Thanks, speeves

So these are the versions required to run properly with mod_perl 2.0?
Here is an updated table:

Module Name Required Dist Package
-
Apache::AuthExpire Apache-AuthExpire-0.38
Apache::AuthNetLDAPApache-AuthNetLDAP-0.25
Apache::AuthPerLDAPApache-AuthPerLDAP-2.01
Apache::AuthenNIS Apache-AuthenNIS-0.11
Apache::AuthenPasswd Apache-AuthenPasswd-0.12
Apache::AuthenSmb Apache-AuthenSmb-0.70
Apache::AuthzNIS Apache-AuthzNIS-0.11
Apache::AuthzNetLDAP Apache-AuthzNetLDAP-0.07
Apache::AuthzPasswdApache-AuthzPasswd-0.11
Apache::Clean Apache-Clean-2.00_4 (not released)
Apache::Peek Apache-Peek-1.01
CGICGI.pm-2.93
CGI::CookieCGI.pm-2.93 (comes in the CGI dist)
I can't see Apache-AuthenNTLM-2.04 being ported yet, though. Here is
the list of modules that are being in progress of being ported:
Hi!

Apache-AuthenNTLM-2.04 is indeed ported, I guess I just didn't make a
formal announcement. People can download it from the CPAN site under
my name.

speeves
cws

--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html

Re: AuthenNTLM

2003-08-27 Thread Shannon Eric Peevey

Brett Hales wrote:

I am having problems with Apache-AuthenNTLM-0.23. In apache's error.log
I am getting the following errors reported.
AuthenNTLM: timed out while waiting for lock (key = 23754)

This also seems to cause the web server to go _very_ slow. I have looked
through the AuthenNTLM.pm and found the section where this is evaluated.
There is a comment above it.
# smb aborts any connection that where no user is looged on as soon as somebody
# tries to open another one. So we have to make sure two request, do not start
# two auth cycles at the same time. To avoid a hang of the whole server
we wrap it with
# a small timeout
Maybe this is actually happening and I am getting two auth cycles.

Does anybody have an idea why this is happening?

Thanks,

 

It's possible, but seems unlikely.  Is this happening constantly? 

Also, try messing with the "PerlSetVar ntlmsemkey" and "PerlSetVar 
ntlmsemtimout" values.   "ntlmsemkey" turns serialization on/off, and 
"ntlmsemtimout" sets the timeout for the Apache server to wait for the 
semaphore, (which serializes the requests to the SMB server). 

speeves
cws


--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html

Re: Apache::AuthenNTLM module with HP/Apache

2003-08-14 Thread Shannon Eric Peevey

Antony Batten wrote:

Hi,

Sorry to direct email you, but I am desperate, and was hoping the solution
to the problem below would be a quick one from the people who wrote the
module ;)
Thanks,
Antony.
Appologies if this is no longer your domain, but 

[posted to comp.infosystems.www.servers.unix & comp.lang.perl.modules]

We are trying to use the Apache::AuthenNTLM perl module with HP/Apache and
mod_perl. We have prevented mod_perl from running our cgi-perl scripts (by
using Apache directives to only use mod_perl for *PL files), as we want to
use 5.8 for this, and the HP-supplied mod_perl is tied to 5.6.1
Everything installs ok & the server starts ok. However, we get the following
errors in the errorlog:
[Fri Aug 08 13:39:47 2003] [error] failed to resolve handler
`Apache::AuthenNTLM' [Fri Aug 08 13:39:47 2003] [error] [client
30.254.43.59] Can't find 'boot_Authen__Smb' symbol in
/opt/perl5.8/lib/site_perl/5.8.0/ PA-RISC1.1/auto/Authen/Smb/Smb.sl
Compilation failed in require at
/opt/perl5.8/lib/site_perl/5.8.0/PA-RISC1.1/Apache/AuthenNTLM.pm line 29.
BEGIN failed--compilation aborted at
/opt/perl5.8/lib/site_perl/5.8.0/PA-RISC1.1/Apache/AuthenNTLM.pm line 29.
Compilation failed in require at (eval 5) line 3.
Looks an odd error, as the symbol seems to be there (I am no programmer
though :)
[EMAIL PROTECTED] $ nm
/opt/perl5.8/lib/site_perl/5.8.0/PA-RISC1.1/auto/Authen/Smb/Smb.sl | grep
boot
boot_Authen__Smb |30816|extern|entry |
boot_Authen__Smb |30936|extern|code |$CODE$
Does anyone know what is causing the problem? 
We are really stumped here and I am up against a deadline to get this stuff
working. All help greatly appreciated 

perl version 5.8.0
mod_perl version 5.6.1
Apache::AuthenNTLM version 2.04
Server version: HP Apache-based Web Server/2.0.43 

 

Can you give us the correct version of mod_perl?  (It should be 1.2x or 
1.99x)

thanks,
speeves
cws

Re: Apache::AuthenNTLM module with HP/Apache

2003-08-14 Thread Shannon Eric Peevey

Antony Batten wrote:

Randy,

OK thanks, I'll give that a try. I think we can compile the module against
5.6.1  It's just that we can't change the 5.6.1 install as it would
break our support agreement with HP (so I am told) ... I presume we just
have to 'install' the module in a different place after compiling it...
Thanks v. much to all for helping me with this.

Rgds,
Antony
-Original Message-
From: Randy Kobes [mailto:[EMAIL PROTECTED] 
Sent: 14 August 2003 07:23
To: Antony Batten
Cc: 'Shannon Eric Peevey'; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Apache::AuthenNTLM module with HP/Apache

On Wed, 13 Aug 2003, Antony Batten wrote:

 

Shannon,

Thanks very much for the quick response. Here's the info you wanted (I
hope):
HP-UX_Apache-based_Web_Server/2.0.46 (Unix) mod_perl/1.99_09 
Perl/v5.6.1 DAV/2 configured

Can my career be saved? ;0)

Thanks again,
Antony.
-Original Message-
From: Shannon Eric Peevey [mailto:[EMAIL PROTECTED]
Sent: 13 August 2003 14:41
To: Antony Batten
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Apache::AuthenNTLM module with HP/Apache
Antony Batten wrote:
   

[ .. ]
 

We are trying to use the Apache::AuthenNTLM perl module with 
HP/Apache and mod_perl. We have prevented mod_perl from running our 
cgi-perl scripts (by using Apache directives to only use mod_perl for 
*PL files), as we want to use 5.8 for this, and the HP-supplied 
mod_perl is tied to 5.6.1

Everything installs ok & the server starts ok. However, we get the 
following errors in the errorlog:

[Fri Aug 08 13:39:47 2003] [error] failed to resolve handler 
`Apache::AuthenNTLM' [Fri Aug 08 13:39:47 2003] [error] [client 
30.254.43.59] Can't find 'boot_Authen__Smb' symbol in 
/opt/perl5.8/lib/site_perl/5.8.0/ PA-RISC1.1/auto/Authen/Smb/Smb.sl 
Compilation failed in require at 
/opt/perl5.8/lib/site_perl/5.8.0/PA-RISC1.1/Apache/AuthenNTLM.pm line 
29. BEGIN failed--compilation aborted at 
/opt/perl5.8/lib/site_perl/5.8.0/PA-RISC1.1/Apache/AuthenNTLM.pm line 
29. Compilation failed in require at (eval 5) line 3.
 

I'm not sure I'm following your setup - is the mod_perl
you're trying to use here compiled under Perl 5.6.1? And Apache::AuthenNTLM
was compiled under Perl 5.8.0? That combination probably won't work in
principle, as 5.6.1 and 5.8.0 are binary incompatible. If you're tied to
mod_perl compiled under 5.6.1, try compiling and using an Apache::AuthenNTLM
compiled under 5.6.1.
 

Thanks, Randy!  (I just woke up in the middle of the night with the same 
answer :)) )

Yes, use the perl binary that points to 5.6.1 when you run 
"/path/to/perl5.6.1 Makefile.PL".  (Running the rest of the install as 
normal, of course ;) )  This will place the module in the appropriate 
location for your mod_perl, that apache is using, to find it.

speeves
cws

Apache-AuthPerLDAP beta port uploaded

2003-08-04 Thread Shannon Eric Peevey

Hi!

I just wanted to see of Henrik Strom was on this list   (I have 
ported your Apache-AuthPerLDAP, and wonder how you want to integrate the 
changes into your existing module.)

Also, I have ported Apache-AuthPerLDAP to work with both versions of 
mod_perl, but am running out of time to set up the test environment.   
If some of you could test the new module, and send documentation of any 
problems with either mod_perl 1 or 2 to me, that would be greatly 
appreciated :)  I have uploaded the ported module to CPAN, and you 
should be able to find it at:

http://search.cpan.org/author/SPEEVES/

later today.

Thanks for your help!!!

speeves
cws
The uploaded file

   Apache-AuthPerLDAP-2.01.tar.gz

has entered CPAN as

 file: $CPAN/authors/id/S/SP/SPEEVES/Apache-AuthPerLDAP-2.01.tar.gz
 size: 4442 bytes
  md5: 1be5678c357fc98723e60374b47932c1

[MP1 and MP2] Apache::AuthzNIS ported

2003-08-01 Thread Shannon Eric Peevey

The uploaded file

   Apache-AuthzNIS-0.11.tar.gz

has entered CPAN as

 file: $CPAN/authors/id/S/SP/SPEEVES/Apache-AuthzNIS-0.11.tar.gz
 size: 4305 bytes
  md5: 37bbbdc320c6bba7318d817e854bc8e1
Apache::AuthzNIS - mod_perl NIS Group Authorization module has been ported to work with both versions of modperl.

thanks,
speeves

[MP1 and MP2] Apache-AuthenNIS ported

2003-08-01 Thread Shannon Eric Peevey

The uploaded file

   Apache-AuthenNIS-0.11.tar.gz

has entered CPAN as

 file: $CPAN/authors/id/S/SP/SPEEVES/Apache-AuthenNIS-0.11.tar.gz
 size: 4095 bytes
  md5: cac172a46c5b05034842fad5eed6b9be
Apache::AuthenNIS - mod_perl NIS Authentication module has been ported to work with both versions of modperl.

thanks,
speeves
cws

Re: [OT] About XML and Petal (was Re: templating system opinions (axkit?))

2003-07-30 Thread Eric Cholet

Le lundi, 28 juil 2003, à 21:27 Europe/Paris, Jean-Michel Hiver a écrit 
:

Also, with TT you have to use the filter 'html' to XML encode your
variables. Petal does it by default, and you need to use the TALES
'structure' keyword to NOT encode.
You don't *have* to use the 'html' filter in TT. I wrote a subclass of
Template which does this automatically for me, and as with Petal I can
also not encode by using a specific method.
--
Eric Cholet

[MP1 and MP2] Apache-AuthenSmb ported

2003-07-28 Thread Shannon Eric Peevey

Hi!

The uploaded file

   Apache-AuthenSmb-0.70.tar.gz

has entered CPAN as

 file: $CPAN/authors/id/S/SP/SPEEVES/Apache-AuthenSmb-0.70.tar.gz
 size: 4004 bytes
  md5: ac1b1a29f5070f81efb9f1362b5815dc
Apache::AuthenSMB - mod_perl NT Authentication module has now been ported to work with both versions of modperl.  I have just uploaded it, so should be available from CPAN in a few hours.

thanks,
speeves
cws

re: AuthenNTLM - help

2003-07-25 Thread Shannon Eric Peevey

Shannon,
i put it working on Solaris, mod_perl, NTLM and mod_jk2 (to comunicate 
with Tomcat), but unfortunatily, it just works when i access from 
windows 9x and Linux. When i access by NT/2000/XP, it just doesn't work 
at all (no validation). So, i decide, for a while, make it work on 
Linux! I am using Conectiva 8, and it is working fine.
Thanks.

Shannon Eric Peevey escreveu:

Francisco de Assis Tristão wrote:

Shannon,
i got it configured with apache-1.3.27/mod_ssl/2.8.12 OpenSSL/0.9.6g 
mod_perl/1.25", all by hand,
but it only works fine when i use just http - when i access the pages 
with https, apache doesn't ask for the user...
Have you any idea about what is wrong?
The version of apache with mod_ssl i took from sunfreeware, mod_perl 
and ApacheAuthenNTLM i compiled by myself.


Sorry, I don't know why this might be happening...  Are you running 
through a proxy server?  I have seen a lot of problems when ntlm 
authentication through a proxy server...

speeves
cws
I am forwarding this to the modperl list...  Please include the list in 
your replies.

thanks,
speeves
cws

Re: modperl2 Apache::HTTP_FORBIDDEN and Apache::HTTP_INTERNAL_SERVER_ERRORimplemented?

2003-07-25 Thread Shannon Eric Peevey

Stas Bekman wrote:

Shannon Eric Peevey wrote:
[...]
*handler = MP2 ? \&handler2 : \&handler1;

I am leaving the MP2 code in both of the subroutines, as I don't know 
if there is a prettier way to do this...  (I will remove it, if there 
is not)

Although this hasn't been tested extensively, it should be working 
fine now.

thanks for the help!
speeves
cws
PS  It did complain about "Prototype mismatch: sub 
Apache::AuthenNTLM::handler vs ($$) at 
/usr/local/lib/perl/5.6.1/Apache/AuthenNTLM.pm" until I added the 
code into both subroutines. 


I've added a new section to the porting tutorial that shows examples 
of how to handle this situation:
http://perl.apache.org/docs/2.0/user/porting/porting.html#Method_Handlers

I changed the code for Apache-AuthenNTLM-2.04 to reflect your example, 
and it works great! 
Thanks for the pointer :)

speeves
cws

Re: Application design patterns

2003-07-24 Thread Eric Sammer

Perrin Harkins wrote:
On Thu, 2003-07-24 at 02:18, Eric Sammer wrote:

where did you (Perrin) keep 
objects like your database handle (assuming DBI, but please correct 
otherwise) and any objects that could be reused (TT, XML parser objects, 
et al)?
People seem to ask about this frequently, but I don't think we did
anything especially interesting there.  We just had a simple class full
of accessors for these resources that would call factory methods the
first time and then cache the result as appropriate.
Sorry to be so cliche / predictable. ;)

This is what I'm sure will wind up happening. I think what I'm looking 
for will require this kind of framework.

This caches the database handle for the rest of the request (one
Apache::DBI ping per request should be enough).
Maybe a stupid question, but what would be the functional difference 
between dumping the object after each request like you say and using the 
same method as you describe for the TT object below? I ask because I'm 
currently treating both objects the same way in two or three of my 
larger applications. I would assume this is to catch premature database 
shutdown or network trouble between an app server and database (cluster) 
on a request by request basis? Is this a performance related choice or 
an Apache::DBI best practices thing?

For the Template Toolkit object we want to cache it for the life of the
process, so it would be something like this:
Right. This is what I currently do.

I see a reference to a utility style class (ESR::Util, IIRC), but after 
rereading a number of articles and design pattern books, I'm reluctant 
to go with a "handle holder" object as I've done in the past.
Gang of Four got you spooked?  If you have something that works and
doesn't cause problems elsewhere in your code, don't fret about it.
Quite true. I think when starting any new large application, as I am 
now, I like to reevaluate my current design methods and look at anything 
I might have been able to do better and do it - a bad (or good) habit.

He who feels he got it right in the past never looks for a better way to 
do it in the future and, thus, stunts all learning and growth... or some 
 such idealistic babble. ;)

That said, I think what I'm learning here is that the uncomfortability 
with this design method is more in my head than tangible.

What I'd like is to have my model (as in MVC) objects reuse the 
process or maybe even server shared objects without doing any of these:

1. Using a singleton utility class
2. Needing to pass objects to model objects' new() in teh controllers
3. Instantiating the objects in the model classes themselves
All of those sound legit to me, as long as you don't duplicate code
between the objects.  I would choose #1, personally.
Yea... that seems to be the ticket, so to speak.

I guess I could use a class to just act as a namespace to hold the 
objects and create them at server startup time and use a module like 
IPC::MM, File::Cache, or Cache::Mmap but that feels kludgy and offers no 
encapsulation for the objects themselves.
No, you can't share things like this between processes.  Things with XS
code, open sockets, filehandles, etc. are not shareable.
And now that you mention it, it seems so obvious. $Deity only knows what 
I was thinking...

Perrin - Have you ever considered revealing more about the Etoys project 
or just the concepts as you applied them? It would be nice to peek at 
some of the details. Or, is this an NDA situation or some such thing? 
Well, I don't have permission to go posting big chunks of code, but in
terms of the generally applicable ideas, I think the article covered
most of it.  The rest has to do with database work and patterns for
building model objects, and I hope to cover that in the article version
of the talk I gave about object-relational mapping tools at this year's
Perl Conference.
Is this past tense and if so, is the article up somewhere? Just curious...

The biggest thing the article didn't cover is the ideas used by the guys
coding the more interactive parts of the application to express the
state machine implemented by each of their modules in a declarative data
structure.  This was largely invented by Adam Sussman, who is at
TicketMaster now.  It was similar to what you see in CGI::Application
and some of the other frameworks.
Hm... that is interesting as well. I've been poking at the internals of 
  a lot of the "frameworks" out there and there are some fantastic 
concepts (Chris Winters' OI comes to mind). Or, there is the distinct 
possibility that I'm overly obsessed with architecture; that shouldn't 
be dismissed either... ;)

Thanks for all your input and the great article(s).
--
Eric Sammer
[EMAIL PROTECTED]
http://www.ineoconcepts.com

Re: Application design patterns

2003-07-24 Thread Eric Sammer

Aaron Ross wrote:
Hi Eric,

class. What I'd like is to have my model (as in MVC) objects reuse the 
process or maybe even server shared objects without doing any of these:

1. Using a singleton utility class
2. Needing to pass objects to model objects' new() in teh controllers
3. Instantiating the objects in the model classes themselves
I'm not sure if this violates 3 (the models classes have to know what
resources they need, so i am not sure what wouldn't), but could you use
a singleton for the resource and a factory to access it? The model
classes call a "static" factory method that handles the configuration,
cache, etc...
This is what I'm thinking I'll do. It seems to be the most "natural" in 
this case. I was reading this paper by Andy Wardly 
http://www.template-toolkit.org/tpc5/camelot/index.html which has a 
collection of resource classes that seem to act in a similar method at 
some level (providing a resource with a class that could be implemented 
as a singleton).

This solves the problem of having configuration and resource allocation
code in your model objects. It does mean that you have to write factory
classes for your resources, but they ought to be quite simple. 
Writing factory methods compared to littering code with instantiation of 
objects all objects are going to need lends itself to an easy and 
obvious first choice. ...For me, at least. ;)

I've done a fair amount of Objective-C (Mac OS X Cocoa and Openstep) and 
there's a number of classes that work in a similar fashion - simple, 
clean, and functional. The reason I like it is because I don't need to 
worry about passing stuff around - just get a static instance and go to 
town. (For those interested or in the know, I'm talking about 
NSNotificationCenter, NSFileManager, and other similar classes).

Thanks for the input!

--
Eric Sammer
[EMAIL PROTECTED]
http://www.ineoconcepts.com

Re: Application design patterns

2003-07-23 Thread Eric Sammer

Perrin Harkins wrote:
There are tutorials on the Template Toolkit site, a recent perl.com
article about TT and Class::DBI, and my article:
http://perl.apache.org/docs/tutorials/apps/scale_etoys/etoys.html
I read Perrin's case study awhile ago and it was excellent. Out of 
curiosity (and since most of my code written prior to reading said 
article looks identical in structure) where did you (Perrin) keep 
objects like your database handle (assuming DBI, but please correct 
otherwise) and any objects that could be reused (TT, XML parser objects, 
et al)?

I see a reference to a utility style class (ESR::Util, IIRC), but after 
rereading a number of articles and design pattern books, I'm reluctant 
to go with a "handle holder" object as I've done in the past. I use a 
configuration object that parses and holds all site config info (DBI 
dsn, user, pass, TT paths, etc.), when apache starts - a singleton style 
class. What I'd like is to have my model (as in MVC) objects reuse the 
process or maybe even server shared objects without doing any of these:

1. Using a singleton utility class
2. Needing to pass objects to model objects' new() in teh controllers
3. Instantiating the objects in the model classes themselves
I guess I could use a class to just act as a namespace to hold the 
objects and create them at server startup time and use a module like 
IPC::MM, File::Cache, or Cache::Mmap but that feels kludgy and offers no 
encapsulation for the objects themselves.

I'm sure I'm either overcomplicating the situation to some great 
extentent or the utility class is the way to go (combined with some 
caching / shared mem module). Is there some obvious pattern I've missed 
or should I just KISS?

Perrin - Have you ever considered revealing more about the Etoys project 
or just the concepts as you applied them? It would be nice to peek at 
some of the details. Or, is this an NDA situation or some such thing? 
Either way, great article.

Thanks in advance.
--
Eric Sammer
[EMAIL PROTECTED]
http://www.ineoconcepts.com

Re: AW: AW: Apache:AuthenNTLM 2.01 with modperl 1.26

2003-07-23 Thread Shannon Eric Peevey

Tresp, Wilfried wrote:

Hi Shannon Eric,

forget my last mail. It is simply to late. After changing PerlModule to
PerlResponseHandler in httpd.conf everything works now. Great!
Only little problem is that I see many error_log entries like the following:

[12163] the $self->{smbhandle} is 903424

ntlmdebug is set to 0

Maybe the line 198 of AuthenNTLM.pm is the reason for this:

   print STDERR "[$$] the \$self->{smbhandle} is $self->{smbhandle}\n";

Regards,	Wilfried

 

Hi!

Glad that it's working now :)  The entries in the error log are just my 
debugging crap that I was using when I was porting.  I will clean up the 
code a little more and upload a new version tomorrow.

Thanks for all of your input!!!
speeves
cws

Re: AW: AW: Apache:AuthenNTLM 2.01 with modperl 1.26

2003-07-23 Thread Shannon Eric Peevey

Tresp, Wilfried wrote:

Hi Shannon Eric,

fine it's already there. I try to run the module with Apache 2.0.47 but it
didn't work here. There seems to be problems with my @INC variable but I can
not figure out how to fix it. When I try to start the daemon I see only the
following error message:
# /usr/local/apache2/bin/apachectl start
[Thu Jul 24 01:27:30 2003] [error] Can't locate Apache/AuthenSmb.pm in @INC
(@INC contains: /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/Apache2
./Apache2 /usr/local/lib/perl5/5.6.1/sun4-solaris /usr/local/lib/perl5/5.6.1
/usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris
/usr/local/lib/perl5/site_perl/5.6.1 /usr/local/lib/perl5/site_perl .
/usr/local/apache2/ /usr/local/apache2/lib/perl) at (eval 4) line 3.
[Thu Jul 24 01:27:30 2003] [error] Can't load Perl module Apache::AuthenSmb
for server netweb.de.kworld.kpmg.com:8000, exiting...
The module AuthenSmb.pm doesn't exist but I can not locate the problem. Do
you have any hints for me?
 

Hi!

Looks to me like you are trying to load Michael Parker's 
Apache::AuthenSmb module...  I don't believe that that mod is ported to 
mp2.   The Authen::Smb module is included with the Apache::AuthenNTLM 
module, so should have been installed when you ran the script.  If you 
change the module that you are trying to load Apache::AuthenNTLM, does 
that help?

speeves
cws
PS  Can you reply to the modperl mailing list?  Thanks :)

Re: AW: Apache:AuthenNTLM 2.01 with modperl 1.26

2003-07-23 Thread Shannon Eric Peevey

Tresp, Wilfried wrote:

Hi,

works now, thanks, next I'll try it with Apache2. AuthenNTLM was the only reason I have not tried it yet :)

Regards,	Wilfried

-Ursprüngliche Nachricht-
Von: Shannon Eric Peevey [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 23. Juli 2003 20:50
An: Tresp, Wilfried
Betreff: Re: Apache:AuthenNTLM 2.01 with modperl 1.26
Tresp, Wilfried wrote:

 

Hello Shannon Eric,

as far as I understood the changes between Apache::AuthenNTLM 2.01 and the
older 0.23 from Gerald Richter your enhancements should make it possible to
use the modul with modperl 1.26 and modperl 2 also, is this right?
I tried to install your version with Apache 1.26, mod_perl 1.27 running
Solaris 8 with Perl 5.6.1 but every time a page is called which requires
authentication I get an internal Server Error and the error_log shows the
following entry:
[Wed Jul 23 20:12:36 2003] [error] Can't locate object method "log" via
package "Apache" (perhaps you forgot to load "Apac
he"?) at
/usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/Apache/AuthenNTLM.pm line
598.
Do you know what happens?  

Regards,

Wilfried Tresp

   

Hi!

Try this file.  Just replace your AuthenNTLM.pm file that the install 
placed in your perl modules directory with this one.  It seems that 
there was a problem here:

if ($type == 1)
   {
597 --># my $log = $r->log;
   my $nonce = $self -> get_nonce ($r) ;
in the first handler subroutine at line 597...  I have commented out the 
line, and it should work now.

Thanks for the heads-up :)

speeves
cws
 

Great!!!  I will upload a fixed version to CPAN, and it should be 
available after a few hours.

speeves
cws

Re: Templating system opinions (CGI::Application in connection with either HTML::Template or Template::Toolkit)

2003-07-23 Thread Eric

Hi,

That was really interesting to look at. OpenInteract is really impressive. 
I guess there is always a cost to having a big
do it all type of system. That is what made me avoid Mason, it just blew my 
head off for complexity. Now it is true, I am looking for a bit more than 
what CGI::Application offers out of the box, but it may well end up being 
worthwhile to just extend rather than convert. I really appreciate the 
simple philosophy that HTML::Template and CGI::Application follow.

One question, how do you judge that OpenInteract is more established? Is 
does look like it is actively developed, but I never heard of it before, 
and I couldn't find much indication of how popular it is.



Thanks,

Eric

At 09:23 AM 2003-07-23, Randal L. Schwartz wrote:
>>>>> "Dave" == Dave Baker <[EMAIL PROTECTED]> writes:

Dave> I'm curious as to why the combination of CGI::Application and
Dave> HTML::Template hasn't taken off ... CGI::Application seems to allow a
Dave> software developer to create an entire CGI app that can be stored and
Dave> distributed as a module on CPAN, but only a couple such app/modules
Dave> have been so added.
Maybe because it competes with OpenInteract, which is far more established.

--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<[EMAIL PROTECTED]> http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
Lead Programmer
D.M. Contact Management
250.383.0836

Re: AuthenNTLM - Help

Francisco de Assis Tristão wrote:

Shannon,
i got it configured with apache-1.3.27/mod_ssl/2.8.12 OpenSSL/0.9.6g 
mod_perl/1.25", all by hand,
but it only works fine when i use just http - when i access the pages 
with https, apache doesn't ask for the user...
Have you any idea about what is wrong?
The version of apache with mod_ssl i took from sunfreeware, mod_perl 
and ApacheAuthenNTLM i compiled by myself.
Sorry, I don't know why this might be happening...  Are you running 
through a proxy server?  I have seen a lot of problems when ntlm 
authentication through a proxy server...

speeves
cws

[mp2] beta of Apache-AuthenNTLM uploaded

The uploaded file

   Apache-AuthenNTLM-2.01.tar.gz

has entered CPAN as

 file: $CPAN/authors/id/S/SP/SPEEVES/Apache-AuthenNTLM-2.01.tar.gz
 size: 50644 bytes
  md5: f175a98ea668e81df9cc8d6db629facf
The purpose of this module is to perform a user authentication via Mircosoft's
NTLM protocol.  (This module also implements Basic Authentication for all other 
browsers ).
You may download this beta version of Apache-AuthenNTLM from CPAN.  It is not a replacement for the existing version on CPAN, but instead will work with either version of modperl.  Please, feel free to download it and send me any bug reports... :)

thanks,
speeves
cws

Re: modperl2 Apache::HTTP_FORBIDDEN... [long post]

Stas Bekman wrote:

Shannon Eric Peevey wrote:



use constant MP2 => ($mod_perl::VERSION >= 1.99);

# test for the version of mod_perl, and use the appropriate libraries
BEGIN {
   if (MP2) {
   require Apache::Const;
   require Apache::Access;
   require Apache::Connection;
   require Apache::Log;
   require Apache::RequestRec;
   require Apache::RequestUtil;
   apache::Const->import(-compile =>
  


 ^
This might be a typo, but if you change that to Apache::Const
(upper case 'A'), does that help?
 

Fantastic!!!  I have been staring at all of the wrong code for way 
too long... :P

Thanks for taking the time to find my error :)

I should have a working version by the beginning of next week.


I think that this still won't work. The reason:

 Apache::Const->import(-compile => 
'HTTP_UNAUTHORIZED','HTTP_INTERNAL_SERVER_ERROR','DECLINED','HTTP_FORBIDDEN','OK'); 

only compiles the constants, it doesn't import them. Drop the 
'-compile =>' part, and then they will be imported. -compile tell 
Apache::Const to not import the constants but to compile them.

It did work, in fact.  (I was just snoozing on the job... :P )  

Thanks, Randy!

speeves
cws

Re: modperl2 Apache::HTTP_FORBIDDEN and Apache::HTTP_INTERNAL_SERVER_ERRORimplemented?



Though I seem to be chasing it down to a possible problem with the 
method handler:

sub handler ($$)

But even with a change to:

sub handler : method


This is an interesting one. How to make the two coexist in the same 
code base. Ideally you want to do this:

sub handler1 ($$) {}
sub handler2 : method {}
*handler = MP2 ? \&handler2 : \&handler1;

But probably it'll complain about different prototypes. Or it might 
just work. Give it a try.


Hi!

Looks like your example will work, though, it is kind of messy, 
(probably because I don't completely follow the example).  I basically 
added the handler code into the subroutines as defined:

sub handler1 ($$) {  
   my ($class, $r) = @_ ;
   my $type ;
   my $nonce = '' ;
   my $self ;
   ...
}

sub handler2 : method
  {
   my ($class, $r) = @_ ;
   my $type ;
   my $nonce = '' ;
   ...
}
*handler = MP2 ? \&handler2 : \&handler1;

I am leaving the MP2 code in both of the subroutines, as I don't know if 
there is a prettier way to do this...  (I will remove it, if there is not)

Although this hasn't been tested extensively, it should be working fine now.

thanks for the help!
speeves
cws
PS  It did complain about "Prototype mismatch: sub 
Apache::AuthenNTLM::handler vs ($$) at 
/usr/local/lib/perl/5.6.1/Apache/AuthenNTLM.pm" until I added the code 
into both subroutines.

Re: Values of an array..

2003-07-21 Thread Eric Wong

On Mon, Jul 21, 2003 at 02:38:20PM -0700, Andrew Hurst wrote:
> At 01:22 PM 7/21/2003 -0800, Dennis Stout wrote:
> >> >"Dennis Stout"  wrote ...
> >> > my %user_list = get_users($where);
> >> >
> >> > foreach (keys %user_list) {
> >> > my $user = $_;
> >> > foreach (@{$user_list{$user}{DOMAIN}}) {
> >> > $user_list{$user}{DOMAINS} .=
> >> >"$user_list{$user}{DOMAIN}[$_],";
> >> > }
> >> > chop($user_list{$user}{DOMAINS});
> >> >...
> >>
> >> >$user_list{$user}{DOMAINS} .= "$user_list{$user}{DOMAIN}[$_],";
> >>
> >> That line is the culprit.  $_ contains each domain name as a text
> >> string.  Which evaluates to 0 when used as an integer, which then gives 
> >the
> >> first entry in the array.  Thus you get the first entry in the array as
> >> many times as you have entries in the array.  Try changing that to a
> >> regular (indexed) for loop and that should fix it.
> >
> >Good eye, I was too busy thinking of hashes and things.
> >
> >I hate array's.
> >
> >Should just be $user_list{$user}{DOMAINS} .= "$_,"; huh?
> 
> Yep.  After I sent the last email I realized that suggesting an indexed
> for loop was more effort than just deleting part of the string already
> there, like you just suggested.

This would be a good place for a join (perldoc -f join):

$user_list{$user}{DOMAINS} = join ',', @{$user_list{$user}{DOMAIN}};

which lets you do away with the trailing chop() as well.

Since this has nothing to do with mod_perl, if you must reply, please
do it off-list.

Eric

small doc typo...

2003-07-21 Thread Shannon Eric Peevey

Hi!

Just perusing:

http://perl.apache.org/docs/2.0/devel/core/apache_integration.html#The_Link_Between_mod_perl_and_httpd

and found a small typo.

"STANDARD20_MODULE_STUFF is a standard macro defined in 
httpd-2.0/include/http_config.h. Currently its main use *if* for 
attaching Apache version magic numbers,"

Probably mean, "Currently its main use *is *for..."

thanks,
speeves
cws

Calling a mod_perl method from whithin a CGI script

2003-07-20 Thread Eric Ricardo Anton

	I have started using Apache::AuthCookie, which runs under mod_perl, for 
authentication. The problem is that the whole website I’m working on is 
based on mod_cgi. I need the CGI scripts to call a mod_perl method in 
order to recognize the user that is logged in.

	Since I can't port the scripts from mod_cgi to mod_perl, how can I make 
a CGI script call a mod_perl method?

	Thanks for any help.

	Eric

Re: modperl2 Apache::HTTP_FORBIDDEN... [long post]

2003-07-17 Thread Shannon Eric Peevey



use constant MP2 => ($mod_perl::VERSION >= 1.99);

# test for the version of mod_perl, and use the appropriate libraries
BEGIN {
   if (MP2) {
   require Apache::Const;
   require Apache::Access;
   require Apache::Connection;
   require Apache::Log;
   require Apache::RequestRec;
   require Apache::RequestUtil;
   apache::Const->import(-compile =>
   

 ^
This might be a typo, but if you change that to Apache::Const
(upper case 'A'), does that help?
 

Fantastic!!!  I have been staring at all of the wrong code for way too 
long... :P

Thanks for taking the time to find my error :)

I should have a working version by the beginning of next week.

speeves
cws

Re: modperl2 Apache::HTTP_FORBIDDEN... [long post]

2003-07-17 Thread Shannon Eric Peevey

Have you imported them?

use Apache::Const compile ->qw(Apache::HTTP_FORBIDDEN);

All the available Apache:: constants are listed here:

http://perl.apache.org/docs/2.0/api/Apache/Const.html



Hi!

I have included the bare minimum of the code from the module, 
(Apache::AuthenNTLM).  It is still  acting as if I have not imported the 
modules, but I have changed "require" to "use", moved the "use" 
statements into various places of the module to see if they would catch 
it, and nothing doing...  I am at the end of my wits.  If someone would 
have a minute to see if they can see why the Constants within the "sub 
handler" would not be found, (though they are imported), that would be a 
great thanks and help :)  I am running apache 2.0.46 and mod_perl 
1.99_09, perl 5.6.1 on a Debian machine.

Thanks in advance,
speeves
cws
package Apache::AuthenNTLM ;

use strict ;
use vars qw{$cache $VERSION %msgflags1 %msgflags2 %msgflags3 %invflags1 
%invflags2 %invflags3 $debug} ;
use warnings ;
no warnings 'redefine';

$VERSION = 0.24 ;

$debug = 0 ;

$cache = undef ;

use MIME::Base64 () ;
use Authen::Smb 0.95 ;
use Socket ;

# here is where we start the new code

use mod_perl ;
# use Apache::Constants qw(:common);
# setting the constants to help identify which version of mod_perl
# is installed
use constant MP2 => ($mod_perl::VERSION >= 1.99);
# test for the version of mod_perl, and use the appropriate libraries
BEGIN {
   if (MP2) {
   require Apache::Const;
   require Apache::Access;
   require Apache::Connection;
   require Apache::Log;
   require Apache::RequestRec;
   require Apache::RequestUtil;
   apache::Const->import(-compile => 
'HTTP_UNAUTHORIZED','HTTP_INTERNAL_SERVER_ERROR','DECLINED','HTTP_FORBIDDEN','OK');
   } else {
   require Apache::Constants;
   
Apache::Constants->import('HTTP_UNAUTHORIZED','HTTP_INTERNAL_SERVER_ERROR','DECLINED','HTTP_FORBIDDEN','OK');
   }
}
# end modperl code ##



sub handler : method # ($$)
   {
   my ($class, $r) = @_ ;
   my $type ;
   my $nonce = '' ;
   my $self ;
   my $conn = $r -> connection ;
   my $connhdr =  $r -> header_in ('Connection') ;
   my $fh = select (STDERR) ;
   $| = 1 ;
   select ($fh) ;
   my ($addr, $port) = sockaddr_in ($conn -> remote_addr) ;

   print STDERR "[$$] AuthenNTLM: Start NTLM Authen handler pid = $$, 
connection = $$conn conn_http_hdr = $connhdr  main = " . ($r -> main) . 
" cuser = " . $conn -> user .
   ' remote_ip = ' . $conn -> remote_ip . " remote_port 
= " . unpack('n', $port) . ' remote_host = <' . $conn -> remote_host . 
"> version = $VERSION\n" if ($debug) ;

   # we cannot attach our object to the connection record. Since in
   # Apache 1.3 there is only one connection at a time per process
   # we can cache our object and check if the connection has changed.
   # The check is done by slightly changing the remote_host member, which
   # persists as long as the connection does
   # This has to be reworked to work with Apache 2.0
   if (ref ($cache) ne $class || $$conn != $cache -> {connectionid} || 
$conn -> remote_host ne $cache->{remote_host})
   {
   $conn -> remote_host ($conn -> remote_host . ' ') ;
   $self = {connectionid => $$conn, remote_host => $conn -> 
remote_host} ;
   bless $self, $class ;
   $cache = $self ;
   print STDERR "[$$] AuthenNTLM: Setup new object\n" if ($debug) ;
   }
   else
   {
   $self = $cache ;
   print STDERR "[$$] AuthenNTLM: Object exists user = 
$self->{userdomain}\\$self->{username}\n" if ($debug) ;

   if ($self -> {ok})
   {
   $conn -> user($self->{mappedusername}) ;
   # we accept the user because we are on the same connection
   $type = $self -> get_msg ($r);
   my $content_len = $r -> header_in('content-length') ;
   my $method  = $r -> method ;
   print STDERR "[$$] AuthenNTLM: Same connection pid = $$, 
connection = $$conn cuser = " .
   $conn -> user . ' ip = ' . $conn -> 
remote_ip . ' method = ' . $method . ' Content-Length = ' .
   $content_len . ' type = ' . $type . "\n" 
if ($debug) ;

   # IE (5.5, 6.0, probably others) can send a type 1 message
   # after authenticating on the same connection.  This is a
   # problem for POST messages, because IE also sends a
   # "Content-length: 0" with no POST data.
   if ($method eq 'GET' || $method eq 'HEAD' || $method eq 
'OPTION' || $method eq 'DELETE' ||
   $content_len > 0 || $type == 3)
   {
   print STDERR "[$$] AuthenNTLM: OK because same 
connection\n" if ($debug) ;
   return MP2 ? Apache::OK : Apache::Constants::OK ;

Re: modperl2 Apache::HTTP_FORBIDDEN and Apache::HTTP_INTERNAL_SERVER_ERRORimplemented?

2003-07-17 Thread Shannon Eric Peevey

Stas Bekman wrote:

speeves wrote:

Hi!

Just wondering if Apache::HTTP_FORBIDDEN and 
Apache::HTTP_INTERNAL_SERVER_ERROR have been implemented?  I have 
been trying to port Apache::AuthenNTLM, and keep getting:

[Tue Jul 15 16:46:08 2003] [error] failed to resolve handler 
`Apache::AuthenNTLM'
[Tue Jul 15 16:46:08 2003] [error] [client 192.168.1.2] Bareword 
"Apache::HTTP_FORBIDDEN" not allowed while "strict subs" in u
se at /usr/local/lib/perl/5.6.1/Apache/AuthenNTLM.pm line 593.
Bareword "Apache::HTTP_INTERNAL_SERVER_ERROR" not allowed while 
"strict subs" in use at /usr/local/lib/perl/5.6.1/Apache/Authe
nNTLM.pm line 597.
Bareword "Apache::HTTP_INTERNAL_SERVER_ERROR" not allowed while 
"strict subs" in use at /usr/local/lib/perl/5.6.1/Apache/Authe
nNTLM.pm line 632.
BEGIN not safe after errors--compilation aborted at 
/usr/local/lib/perl/5.6.1/Apache/AuthenNTLM.pm line 671.
Compilation failed in require at (eval 10) line 3.

in the error_log.  I have other constants that are imported from 
Apache::Const, so do not think that it is a problem with scope...  
Here is the code:

line 593 --  return $self->{ntlmauthoritative} ? (defined($nonce) ? 
(MP2 ? Apache::HTTP_FORBIDDEN : Apache::Constants::HTTP_
FORBIDDEN) : (MP2 ? Apache::HTTP_INTERNAL_SERVER_ERROR : 
Apache::Constants::HTTP_INTERNAL_SERVER_ERROR)) : (MP2 ? Apache::DE
CLINED : Apache::Constants::DECLINED) ;

and

line 632 --- # return MP2 ? Apache::HTTP_INTERNAL_SERVER_ERROR : 
Apache::Constants::HTTP_INTERNAL_SERVER_ERROR ;

If you need more, let me know.


Have you imported them?

use Apache::Const compile ->qw(Apache::HTTP_FORBIDDEN);

All the available Apache:: constants are listed here:

http://perl.apache.org/docs/2.0/api/Apache/Const.html

Yeah, unfortunately... :(   Though I seem to be chasing it down to a 
possible problem with the method handler:

sub handler ($$)

But even with a change to:

sub handler : method

I'm still not able to access the imported CONSTANTS 
This is definitely the most complex port that I've done, so is taking me 
a little while to find all of the buggies...   Will keep you posted :)

speeves
cws

Re: informational notice in Makefile.PL

Randy Kobes wrote:

On Mon, 14 Jul 2003, Stas Bekman wrote:

[ ... ]
 

Are you talking about the dependencies list? by 'the current
state of affairs with mod_perl 2.0', you mean that it's not
indexed by PAUSE. It's available from CPAN.
Actually, once it gets indexed by CPAN it'll break all the
other modules which specify mod_perl (1.0) as a dependency and
won't work with 2.0.
   

Perhaps it might be an idea, at this stage, to recommend to
module authors that, if their package is for mod_perl 1 only, to
use a module like Apache::Constants in their PREREQ_PM (ie,
something available only within mod_perl 1), and if it's for
mod_perl 2 only, use something like Apache::Const, or something
available only with mod_perl 2. This won't help existing
packages, but it would at least alert people that a problem is on
the horizon.
To help in this, perhaps it would be worthwhile to promote the
use of Module::Install? A package (Module::Install::mod_perl?)
could be made which would make available a function to test for
the mod_perl version a user has, and then decide if this is
appropriate for the package about to be installed. If the
required mod_perl version isn't present, one could either offer
to add the required version to PREREQ_PM, or else just die, as
automated installs of mod_perl can be tricky. A lot of the code
for this could be extracted from Apache::Test; Stas, you've also
worked through this logic in making packages that include
different versions for different mod_perl versions.  Only the
package author need have Module::Install::* when constructing the
Makefile.PL - the necessary stuff for the added functionality is
added to the distribution, making it transparent to the user.
 

Here is an example of my Makefile.PL using ModUtils::AutoInstall:

   # ExtUtils::AutoInstall Bootstrap Code, version 7.
   BEGIN{my$p='ExtUtils::AutoInstall';my$v=0.52;$p->VERSION||0>=$v
   or+eval"use $p $v;1"or+do{my$e=$ENV{PERL_EXTUTILS_AUTOINSTALL};
   (!defined($e)||$e!~m/--(?:default|skip|testonly)/and-t STDIN or
   eval"use ExtUtils::MakeMaker;WriteMakefile(PREREQ_PM=>{'$p',$v}
   );1"and exit)and print"==> $p $v required. Install it from CP".
   "AN? [Y/n] "and!~/^n/i and print"*** Installing $p\n"and
   do{if (eval '$>' and lc(`sudo -V`) =~ /version/){system('sudo',
   $^X,"-MCPANPLUS","-e","CPANPLUS::install $p");eval"use $p $v;1"
   ||system('sudo', $^X, "-MCPAN", "-e", "CPAN::install $p")}eval{
   require CPANPLUS;CPANPLUS::install$p};eval"use $p $v;1"or eval{
   require CPAN;CPAN::install$p};eval"use $p $v;1"||die"*** Please
   manually install $p $v from cpan.org first...\n"}}}
   # notify the user about mod_perl 2
   BEGIN { print q{
    NOTICE *
   If you are planning to use mod_perl2 and Apache2, please, do not
   answer yes when prompted to install mod_perl.  You will need to
   download mod_perl2 manually from
   http://perl.apache.org/download/index.html
   *
   } }
   # optional pre-install handler; takes $module_name and $version
   # sub MY::preinstall  { return 1; } # return false to skip install
   # optional post-install handler; takes $module_name, $version, $success
   # sub MY::postinstall { return; }   # the return value doesn't matter
   # the above handlers must be declared before the 'use' statement
   use ExtUtils::AutoInstall (
   -version=> '0.40',  # required AutoInstall version
   # usually 0.40 is sufficient
   -config => {
   make_args   => '--hello',   # option(s) for CPAN::Config
   force   => 1,   # pseudo-option to force install
   do_once => 1,   # skip previously failed modules
   },
   -core   => [
   Convert::ASN1 => '',
   Net::LDAP => '',
   mod_perl => '',
   ],  # core modules; may also be 'all'
   );
   WriteMakefile(
   AUTHOR  => 'Mark Wilcox ([EMAIL PROTECTED]) and 
Shannon Eric Peevey ([EMAIL PROTECTED])',
   ABSTRACT=> 'Apache::AuthNetLDAP -- Perl module which 
authenticates users via LDAP using the Net::LDAP module.'
,
   NAME=> 'Apache::AuthNetLDAP',
   VERSION_FROM=> 'AuthNetLDAP.pm',
   DISTNAME=> 'Apache-AuthNetLDAP',
   );

I then add the necessary code inside of the .pm file to check the 
version of  mod_perl on the machine and perform appropriately. (I 
hope... ;) )  This allows a module to live in both worlds, and removes 
the necessity of supporting two code bases.  I think that this type of 
porting will help authors to go ahead and port their modules, expanding 
the mp2 module base, and alleviate fears of jumping off of a cliff and 
leaving mp1 behind.

Just my .02...
speeves
cws

Re: AuthenNTLM - Help

Stas Bekman wrote:

Francisco de Assis Tristão wrote:

Frank,
please, i am trying to configure AuthenNTLM on a solaris 2.8 (SPARC)
machine. But i did not find any sample about how to configure
httpd.conf. May you help me? I had compiled apache 2 version 2.0.46 with
ssl suport (i am configuring it with mod_jk and Tomcat too). Do i need
to have mod_perl installed?


You certainly need to have mod_perl installed. This and other 
questions are answered at http://perl.apache.org/.

However I'm not sure whether this module has been ported to mod_perl 
2.0. Therefore you probably need to either port it, or use mod_perl 
1.0, in case it wasn't ported yet.



__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com
I am in the process of porting it now.  Will hopefully have a working 
version in the next couple of days. 

Francisco, check out the documentation using perldoc:

perldoc Apache::AuthenNTLM

There is an example for the httpd.conf configuration in there.

I'll keep you posted on the port, and will announce when and where I 
have a working version.  The author is only excepting patches for the 
mod, so will probably take a little time for him to get my changes 
implemented into the indexed version.  (Will also keep you posted on 
that... :) )

speeves
cws

Re: mod_perl 1.0 and 2.0

Chris Faust wrote:

There is a 0.92 version of Apache::DBI is mp2 aware (there may even be 
a later version at this point).
We started with mp1 and do to problems we decided to goto mp2 (which 
turned out to be non mod_perl and apache related), there wasn't any 
major performance increase or anything like that and I don't remember 
anything major coming up during the switch (outside of cookies - which 
always seem to be a problem).
I use a bunch of the popular modules like HTML::Template, 
Image::Magick, DBI, Parse/WriteExcel, Date::Manip etc and I haven't 
had any problems.
Like Sreeji said, its really about your requirements - but the above 
is my experience, for what its worth.
-Chris

- Original Message -
*From:* Jamie Krasnoo 
*To:* [EMAIL PROTECTED] 
*Sent:* Wednesday, July 09, 2003 3:49 PM
*Subject:* mod_perl 1.0 and 2.0
Hi all,

I’m currently working on a personal project to get myself back in
mod_perl programming order. However I’m more used to using
mod_perl 1.0 with Apache 1.3.x. I’m going through the
documentation for mod_perl 2.0 but I’m worried that most of the
modules I need won’t work with mod_perl 2.0. I’ve been looking for
what modules will and will not work with 2.0 (like Apache::DBI for
pooling connections with MySQL). Would it be a better benefit to
me to switch over to 2.0?
Thanks,

Jamie

We need more help in porting more mods to go with mp2... too ;) Come 
join the fray :)

speeves
cws

Re: module ported and doc addition...

Stas Bekman wrote:

Shannon Eric Peevey wrote:
[...]
Also, you don't realy have to do that. The old ala mp1 style works 
just fine.

use Apache::Const qw(OK DECLINED)

sub handler {

   return OK;
} 


Well...  I must have been smoking crack, 'cause I seem to remember a 
simple:

return  MP2 ? Apache::OK : OK

throwing an error, hence, the change to:

MP2 ? Apache::OK : Apache::Constants::OK

Now that I test it, though, there doesn't seem to be a problem...  :P


May be you haven't been importing the constant. These two aren't the 
same:

use Apache::Const qw(OK DECLINED);
use Apache::Const -compile => qw(OK DECLINED);
the latter only compiles the constants, the former compiles and 
imports it.

[...]

Just started working on Apache-AuthNTLM and came across the cross 
reference that you posted awhile back.  This might be where I got it:

 sub handler {
 # ...
 return MP2 ? Apache::OK : Apache::Constants::OK;
 }
 1;
in the "mod_perl 1.0 and 2.0 Constants Coexistence" section of:

http://perl.apache.org/docs/2.0/user/porting/compat.html#C_Apache__Constants_

speeves
cws

Re: module ported and doc addition...