Re: Help with Apache::Admin::Config Requested

2002-12-30 Thread Olivier Poitrey
"Gene Grimm" <[EMAIL PROTECTED]> writes:

> I resolved the configuration file update problem by going back to
> specifying the file name. I had tried using "new
> Apache::Admin::Config \*HANDLE" (with version 0.55-1) so I could
> 'flock' the file to prevent possible conflicts 

You really should upgrade, the last version is 0.90 and it fix many
bugs.

Also, keep in mind that reading configuration on a Filehandle doesn't
seek it to the beginning after the read. You should have to empty the
FH before calling save() or you should close the FH and save into
another one... This behavior may change in future.

See you

-- 
__
 O  l  i  v  i  e  rP  o  i  t  r  e  y


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Help with Apache::Admin::Config Requested

2002-12-30 Thread Olivier Poitrey
"Gene Grimm" <[EMAIL PROTECTED]> writes:

> I've managed to get the configuration objects doing what I need with
> Apache::Admin::Config except for two things. When I do
> obj->add_blank() it doens't seem to add the blank lines nor does
> conf->save write the configuration to the file. I can see what was
> created by doing a print conf->dump_raw so it is updating the vhost
> and conf objects, but it just won't write to disk. Does anyone have
> any suggestions on what to check for glitches?

Hi Gene,

Please tell me more about the version of AAC you are using, and cut
and past me some code. I can't replicate the glitche.

Be sure that you give an existing configuration file as argument to
the constructor, or if you are starting from a fresh configuration,
you give a filename to the save method. Finally, print the error
string at the failure like this :

   $conf->save() or die print $conf->error();

best regards,

-- 
__
 O  l  i  v  i  e  rP  o  i  t  r  e  y


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Perl module for Apache configuration

2002-11-22 Thread Olivier Poitrey
Craig Sanders <[EMAIL PROTECTED]> writes:

> On Thu, Nov 21, 2002 at 10:34:20AM -0500, Gene Grimm wrote:
>> Are there any Perl modules that can help modify a configuration file
>> for Apache? 
>
> libapache-configfile-perl can parse apache config files.  for writing
> them, you're on your own AFAIK (not very hard, it's plain text with a
> well-defined format, easy to generate).

BTW Apache::Admin::Config does the job with respect of the file
indentation. It's not part of Debian but you can find the debian
package at:

  ftp://ftp.rhapsodyk.net/pub/devel/perl/Apache-Admin-Config/.

This module is 1 year old, and it's ready for production
use. Feedback is welcome.

-- 
__
 O  l  i  v  i  e  rP  o  i  t  r  e  y


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: System locks up with RealTek 8139 and kernel 2.2.20

2001-12-27 Thread Olivier Poitrey
- Original Message - 
From: "Antonio Rodriguez" <[EMAIL PROTECTED]>
To: 
Sent: Friday, December 21, 2001 3:54 PM
Subject: System locks up with RealTek 8139 and kernel 2.2.20

> 2. move to 2.4 and hope this solves the problem. I have already gone
> from 2.2.17 to 2.2.20 to try to fix it, but maybe the move to 2.4 will
> be more significant.

You'll have the same problem with 2.4.x, I have tested it for you :/ 

-- 
___
 O  l  i  v  i  e  rP  o  i  t  r  e  y





Re: System locks up with RealTek 8139 and kernel 2.2.20

2001-12-27 Thread Olivier Poitrey

- Original Message - 
From: "Antonio Rodriguez" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, December 21, 2001 3:54 PM
Subject: System locks up with RealTek 8139 and kernel 2.2.20

> 2. move to 2.4 and hope this solves the problem. I have already gone
> from 2.2.17 to 2.2.20 to try to fix it, but maybe the move to 2.4 will
> be more significant.

You'll have the same problem with 2.4.x, I have tested it for you :/ 

-- 
___
 O  l  i  v  i  e  rP  o  i  t  r  e  y



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]