Opened 8 years ago

Closed 20 months ago

#8400 closed Feature request (worksforme)

Lacking Service Controls over Command Line

Reported by: revin Owned by:
Priority: normal Component: FileZilla Server
Keywords: command line Cc:
Component version: Operating system type: Windows
Operating system version: Microsoft Windows [Version 6.1.7601]

Description (last modified by Tim Kosse)

"FileZilla Server.exe" /active
is not supported.

there are almost no controls over command line
(except /start and /stop),
almost everything must be done through GUI,
and this makes automatic control impossible

as we all know,
FileZilla do have an auto-start option.
but things here is,
the FileZilla Service can be auto-started,
it's not "Active"!

i.e. the Service process is running,
but it won't automatically listen on port 21
(or whatever port in settings)
thus, you have to click "Active" on FileZilla Server Interface every-time after reboot
further more,
I can't find a command line or option to "Active" server automatically

this really makes remote-management suffer!
how can we "click" Active within a .bat script?
and connect to service from localhost (127.0.0.1) still needs authentication, makes it more difficult to develop a TCP plugin to send controls to the service
(not everyone is an expert and have the patience to read all the source code just for an auto-Active feature, isn't it?)

my suggestion is to add more command line support,
at least:
"FileZilla Server.exe" /active
should be supported to Active server automatically within a .bat script

Change History (3)

comment:1 by revin, 8 years ago

Priority: criticalblocker

comment:2 by Tim Kosse, 5 years ago

Description: modified (diff)
Priority: blockernormal

comment:3 by Kurt McKee, 20 months ago

Resolution: worksforme
Status: newclosed

FileZilla Server 0.9.60 is active when the system boots.

Please uninstall and ensure your configuration file is deleted. Then, reinstall the latest version and re-test. If this is still an issue please re-open the ticket. Thanks!

Note: See TracTickets for help on using tickets.