Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#17529 - [pure-ftpd] rc.d handling errors
Attached to Project:
Arch Linux
Opened by Pavel Šiška (punjab) - Wednesday, 16 December 2009, 15:15 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 08 September 2010, 14:43 GMT
Opened by Pavel Šiška (punjab) - Wednesday, 16 December 2009, 15:15 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 08 September 2010, 14:43 GMT
|
DetailsIn configuration file
/etc/pure-ftpd.conf uncoment line: TLS 1 Try start daemon: /etc/rc.d/pure-ftpd start [DONE] But isn't started. In log files: adin pure-ftpd: (?@?) [ERROR] Sorry, but that file doesn't exist: [/etc/ssl/private/pure-ftpd.pem] Can be this handled with rc.d script and reported when somebody try start server instead DONE status? Some works perfectly. For example uncomment line: MySQLConfigFile Reporting FAIL with 421 Unknown authentication method: mysql:/etc/pureftpd-mysql.conf In log file: adin pure-ftpd: (?@?) [ERROR] Unknown authentication method: mysql:/etc/pureftpd-mysql.conf |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Wednesday, 08 September 2010, 14:43 GMT
Reason for closing: Won't fix
Additional comments about closing: see comments
Wednesday, 08 September 2010, 14:43 GMT
Reason for closing: Won't fix
Additional comments about closing: see comments
I start server with init script and no erros reported. Only "DONE" like in situations when server started correctly.
No matter what is needed or what is missing. Server just don't start. I should get error from init script correctly like in MySQLConfigFile option.
If we want intelligent init scripts, then this is IMHO bug. If we don't, close this.
We cannot edit the daemon script to works with every configuration
Maybe just after daemon start check if process is running? If not, then instead DONE status report FAIL.
No matter what is wrong, but we correctly report this to user, which can go to logs look for error description.
I dont have arch right now, so i cant check if process go down in this wrong configuration situations.
If yes, maybe this can be solution?