[BlueOnyx:23087] Re: fixproftpd_conf.pl

[Ken Hohhof]

OK, thanks for the clarification.

It still looks to me like we had those containers in the config from
2014-2019 via the yum updates.  (5208R version)  So even though we always
told siteadmins they needed to cd to /web, some probably ignored that and
got away with it.  You know how people are, instructions are taken as
optional recommendations, especially if there are no penalties.

It looks like the yum update saved a copy of the old config, and it would
probably be safe to cut and paste that into the new config.  Or just tell
the one customer having a problem (they had their site redesigned in 2016)
to change the path to /web.  Seems like either approach would work.


-----Original Message-----
From: Blueonyx <blueonyx-bounces at mail.blueonyx.it> On Behalf Of Michael
Stauber
Sent: Friday, August 2, 2019 6:16 PM
To: blueonyx at mail.blueonyx.it
Subject: [BlueOnyx:23086] Re: fixproftpd_conf.pl

Hi Ken,

> I see this script in /usr/Sausalito/sbin and it seems to do what is 
> says in the comments:
> 
> # $Id: fixproftpd_conf.pl Sat 25 Jan 2014 15:40:02 PM COT mstauber $

This script is deprecated.

Once upon a time we used it after ProFTPd upgrades to add the
<VirtualHost>-containers to proftpd.conf. But we eventually stopped using
the <VirtualHost>-containers altogether, as they were more trouble than it
was worth.

--
With best regards

Michael Stauber
_______________________________________________
Blueonyx mailing list
Blueonyx at mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx