• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

ftp_psa (xinetd => standalone)

nickles

New Pleskian
After disabling ftp_psa with "chkconfig ftp_psa off", how would I add the standalone version (/etc/proftpd.conf.ServerType is standalone now) to the chkconfig database (no proftpd/ftp_psa script in /etc/init.d)?

Of course I could start the server in some rc file, but I want to stay compliant with the procedures.
 
May I ask - what is the reason of this Plesk customization?
 
Glad you ask ;-)

Our server will be a FTP (only) server with a lot of data flowing in and out. So using the standalone version - from my point of view - makes sense.
 
Try to change ServerType and use your standalone startup script:

# grep ServerType /etc/proftpd.conf
#ServerType standalone
ServerType inetd
 
That's what I already did, and, starting proftpd from the command line works (as it would do if I started it from a rc script). However I want to have proftpd be configurable through "chkconfig" and "service"; unfortunately the corresponding script is missing from /etc/init.d (not included in psa-proftpd's RPM).

My hope was/is that s.o. (possibly Parallels i.e. you ;-) can provide an "official" /etc/init.d/proftpd script...
 
What about this script from proftpd package from OS vendor? Does it work?
 
Glad you ask ;-)

Our server will be a FTP (only) server with a lot of data flowing in and out. So using the standalone version - from my point of view - makes sense.

But have you tried to use default Plesk ftp settings? Never heard before about problems with xinet.d cases.
 
I didn't experience any problems so far with the xinetd version, but this server is going to be a FTP server in its own right, so making proftpd a standalone server makes perfectly sense to me. Also, I don't see any problems in such a configuration, so supporting it through the GUI/console should be a no-brainer for PLESK...
 
I have submitted corresponding request to developers (#1782213 for your reference). We will consider possibility for switching service mode and possible advantages of this.
 
Back
Top