|
Titel: Löschen abgebrochener Uploads Beitrag von: NickTheRipper am 23. Oktober 2003, 20:09:09 Ich möchte ganz gerne, daß abgebrochene Downloads automatisch wieder vom Server gelöscht werden, aber es will nicht so recht funktionieren.
Ich habe in der proftpd.conf den Befehl "DeleteAbortedStores on" verwendet und diesen an mehreren Stellen versucht einzubinden, aber vergebens. Der Server selber läuft als "inetd". Ich ließ ProFTD auch im Debugmodus laufen und werden die abgebrochenen Uploads als erfolgreicher Upload angezeigt. Ich erstellte zuerst ein Verzeichnis "test" und simulierte dann einen abgebrochenen Upload, indem ich die Datei "testdatei" auf den Server schob und den Upload dann selber abgebrochen habe. Hier die Debugausgabe: Code: connect from 192.168.0.20 (192.168.0.20) parsing '/etc/proftpd.conf' configuration <Directory />: adding section for resolved path '/' <Directory /upload>: adding section for resolved path '/upload' <Directory /download>: adding section for resolved path '/download' <Directory >: adding section for resolved path '' 192.168.0.1 - 192.168.0.1 - Config for NxB-[Clan]: 192.168.0.1 - / 192.168.0.1 - AllowOverwrite 192.168.0.1 - Umask 192.168.0.1 - TransferLog 192.168.0.1 - RootLogin 192.168.0.1 - DeleteAbortedStores 192.168.0.1 - MaxClientsPerHost 192.168.0.1 - DirFakeMode 192.168.0.1 - RequireValidShell 192.168.0.1 - DefaultServer 192.168.0.1 - TimeoutIdle 192.168.0.1 - TimeoutStalled 192.168.0.1 - TimeoutLogin 192.168.0.1 - TimeoutNoTransfer 192.168.0.1 - AuthPAM 192.168.0.1 - AuthPAMAuthoritative 192.168.0.1 - Umask 192.168.0.1 - UserID 192.168.0.1 - UserName 192.168.0.1 - GroupID 192.168.0.1 - GroupName 192.168.0.1 - DefaultRoot 192.168.0.1 - TransferLog 192.168.0.1 - ExtendedLog 192.168.0.1 - ExtendedLog 192.168.0.1 - RootLogin 192.168.0.1 - IdentLookups 192.168.0.1 - DeleteAbortedStores 192.168.0.1 - RootLogin 192.168.0.1 - MaxLoginAttempts 192.168.0.1 - MaxClientsPerHost 192.168.0.1 - DirFakeMode 192.168.0.1 - RootLogin 192.168.0.1 - RequireValidShell 192.168.0.1 - 192.168.0.1 - Config for NxB-[Clan]: 192.168.0.1 - 192.168.0.1 - /upload 192.168.0.1 - Limit 192.168.0.1 - DenyAll 192.168.0.1 - Limit 192.168.0.1 - AllowAll 192.168.0.1 - GroupOwner 192.168.0.1 - DeleteAbortedStores 192.168.0.1 - AllowOverwrite 192.168.0.1 - Umask 192.168.0.1 - DirFakeMode 192.168.0.1 - MaxClientsPerHost 192.168.0.1 - MaxClients 192.168.0.1 - DisplayLogin 192.168.0.1 - DisplayFirstChdir 192.168.0.1 - TransferLog 192.168.0.1 - RootLogin 192.168.0.1 - RequireValidShell 192.168.0.1 - /download 192.168.0.1 - Limit 192.168.0.1 - DenyAll 192.168.0.1 - AllowOverwrite 192.168.0.1 - Umask 192.168.0.1 - DirFakeMode 192.168.0.1 - MaxClientsPerHost 192.168.0.1 - MaxClients 192.168.0.1 - DisplayLogin 192.168.0.1 - DisplayFirstChdir 192.168.0.1 - TransferLog 192.168.0.1 - RootLogin 192.168.0.1 - DeleteAbortedStores 192.168.0.1 - RequireValidShell 192.168.0.1 - Limit 192.168.0.1 - DenyAll 192.168.0.1 - AllowOverwrite 192.168.0.1 - Umask 192.168.0.1 - DirFakeMode 192.168.0.1 - MaxClientsPerHost 192.168.0.1 - MaxClients 192.168.0.1 - DisplayLogin 192.168.0.1 - DisplayFirstChdir 192.168.0.1 - TransferLog 192.168.0.1 - RootLogin 192.168.0.1 - DeleteAbortedStores 192.168.0.1 - RequireValidShell 192.168.0.1 - Limit 192.168.0.1 - DenyGroup 192.168.0.1 - DefaultRoot 192.168.0.1 - AllowOverwrite 192.168.0.1 - AuthPAM 192.168.0.1 - AuthPAMAuthoritative 192.168.0.1 - Umask 192.168.0.1 - DirFakeMode 192.168.0.1 - MaxClientsPerHost 192.168.0.1 - MaxClients 192.168.0.1 - MaxLoginAttempts 192.168.0.1 - DisplayLogin 192.168.0.1 - DisplayFirstChdir 192.168.0.1 - TransferLog 192.168.0.1 - ExtendedLog 192.168.0.1 - ExtendedLog 192.168.0.1 - RootLogin 192.168.0.1 - DeleteAbortedStores 192.168.0.1 - RootLogin 192.168.0.1 - MaxLoginAttempts 192.168.0.1 - MaxClientsPerHost 192.168.0.1 - DirFakeMode 192.168.0.1 - RootLogin 192.168.0.1 - RequireValidShell 192.168.0.1 - error converting stdin to IPv6 socket: Protocol not available 213.23.130.223 (192.168.0.20[192.168.0.20]) - connected - local : 213.23.130.223:21 213.23.130.223 (192.168.0.20[192.168.0.20]) - connected - remote : 192.168.0.20:4687 213.23.130.223 (192.168.0.20[192.168.0.20]) - FTP session opened. 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'USER xxxxxx' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'USER xxxxxx' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'USER xxxxxx' to mod_auth 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'USER xxxxxx' to mod_auth 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'USER xxxxxx' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PASS (hidden)' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PASS (hidden)' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PASS (hidden)' to mod_auth 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'PASS (hidden)' to mod_auth PAM-warn[5009]: service: ftp [on terminal: <unknown>] PAM-warn[5009]: user: (uid=0) -> xxxxxx [remote: ?nobody@192.168.0.20] PAM-warn[5009]: service: ftp [on terminal: <unknown>] PAM-warn[5009]: user: (uid=0) -> xxxxxx [remote: ?nobody@192.168.0.20] PAM-warn[5009]: service: ftp [on terminal: <unknown>] PAM-warn[5009]: user: (uid=0) -> xxxxxx [remote: ?nobody@192.168.0.20] PAM-unix2[5009]: session started for user xxxxxx, service ftp 213.23.130.223 (192.168.0.20[192.168.0.20]) - 213.23.130.223 (192.168.0.20[192.168.0.20]) - Config for NxB-[Clan]: 213.23.130.223 (192.168.0.20[192.168.0.20]) - 213.23.130.223 (192.168.0.20[192.168.0.20]) - /upload 213.23.130.223 (192.168.0.20[192.168.0.20]) - Limit 213.23.130.223 (192.168.0.20[192.168.0.20]) - DenyAll 213.23.130.223 (192.168.0.20[192.168.0.20]) - Limit 213.23.130.223 (192.168.0.20[192.168.0.20]) - AllowAll 213.23.130.223 (192.168.0.20[192.168.0.20]) - GroupOwner 213.23.130.223 (192.168.0.20[192.168.0.20]) - DeleteAbortedStores 213.23.130.223 (192.168.0.20[192.168.0.20]) - AllowOverwrite 213.23.130.223 (192.168.0.20[192.168.0.20]) - Umask 213.23.130.223 (192.168.0.20[192.168.0.20]) - DirFakeMode 213.23.130.223 (192.168.0.20[192.168.0.20]) - MaxClientsPerHost 213.23.130.223 (192.168.0.20[192.168.0.20]) - MaxClients 213.23.130.223 (192.168.0.20[192.168.0.20]) - DisplayLogin 213.23.130.223 (192.168.0.20[192.168.0.20]) - DisplayFirstChdir 213.23.130.223 (192.168.0.20[192.168.0.20]) - TransferLog 213.23.130.223 (192.168.0.20[192.168.0.20]) - RootLogin 213.23.130.223 (192.168.0.20[192.168.0.20]) - RequireValidShell 213.23.130.223 (192.168.0.20[192.168.0.20]) - /download 213.23.130.223 (192.168.0.20[192.168.0.20]) - Limit 213.23.130.223 (192.168.0.20[192.168.0.20]) - DenyAll 213.23.130.223 (192.168.0.20[192.168.0.20]) - AllowOverwrite 213.23.130.223 (192.168.0.20[192.168.0.20]) - Umask 213.23.130.223 (192.168.0.20[192.168.0.20]) - DirFakeMode 213.23.130.223 (192.168.0.20[192.168.0.20]) - MaxClientsPerHost 213.23.130.223 (192.168.0.20[192.168.0.20]) - MaxClients 213.23.130.223 (192.168.0.20[192.168.0.20]) - DisplayLogin 213.23.130.223 (192.168.0.20[192.168.0.20]) - DisplayFirstChdir 213.23.130.223 (192.168.0.20[192.168.0.20]) - TransferLog 213.23.130.223 (192.168.0.20[192.168.0.20]) - RootLogin 213.23.130.223 (192.168.0.20[192.168.0.20]) - DeleteAbortedStores 213.23.130.223 (192.168.0.20[192.168.0.20]) - RequireValidShell 213.23.130.223 (192.168.0.20[192.168.0.20]) - Limit 213.23.130.223 (192.168.0.20[192.168.0.20]) - DenyAll 213.23.130.223 (192.168.0.20[192.168.0.20]) - AllowOverwrite 213.23.130.223 (192.168.0.20[192.168.0.20]) - Umask 213.23.130.223 (192.168.0.20[192.168.0.20]) - DirFakeMode 213.23.130.223 (192.168.0.20[192.168.0.20]) - MaxClientsPerHost 213.23.130.223 (192.168.0.20[192.168.0.20]) - MaxClients 213.23.130.223 (192.168.0.20[192.168.0.20]) - DisplayLogin 213.23.130.223 (192.168.0.20[192.168.0.20]) - DisplayFirstChdir 213.23.130.223 (192.168.0.20[192.168.0.20]) - TransferLog 213.23.130.223 (192.168.0.20[192.168.0.20]) - RootLogin 213.23.130.223 (192.168.0.20[192.168.0.20]) - DeleteAbortedStores 213.23.130.223 (192.168.0.20[192.168.0.20]) - RequireValidShell 213.23.130.223 (192.168.0.20[192.168.0.20]) - Limit 213.23.130.223 (192.168.0.20[192.168.0.20]) - DenyGroup 213.23.130.223 (192.168.0.20[192.168.0.20]) - DefaultRoot 213.23.130.223 (192.168.0.20[192.168.0.20]) - AllowOverwrite 213.23.130.223 (192.168.0.20[192.168.0.20]) - AuthPAM 213.23.130.223 (192.168.0.20[192.168.0.20]) - AuthPAMAuthoritative 213.23.130.223 (192.168.0.20[192.168.0.20]) - Umask 213.23.130.223 (192.168.0.20[192.168.0.20]) - DirFakeMode 213.23.130.223 (192.168.0.20[192.168.0.20]) - MaxClientsPerHost 213.23.130.223 (192.168.0.20[192.168.0.20]) - MaxClients 213.23.130.223 (192.168.0.20[192.168.0.20]) - MaxLoginAttempts 213.23.130.223 (192.168.0.20[192.168.0.20]) - DisplayLogin 213.23.130.223 (192.168.0.20[192.168.0.20]) - DisplayFirstChdir 213.23.130.223 (192.168.0.20[192.168.0.20]) - TransferLog 213.23.130.223 (192.168.0.20[192.168.0.20]) - ExtendedLog 213.23.130.223 (192.168.0.20[192.168.0.20]) - ExtendedLog 213.23.130.223 (192.168.0.20[192.168.0.20]) - RootLogin 213.23.130.223 (192.168.0.20[192.168.0.20]) - DeleteAbortedStores 213.23.130.223 (192.168.0.20[192.168.0.20]) - RootLogin 213.23.130.223 (192.168.0.20[192.168.0.20]) - MaxLoginAttempts 213.23.130.223 (192.168.0.20[192.168.0.20]) - MaxClientsPerHost 213.23.130.223 (192.168.0.20[192.168.0.20]) - DirFakeMode 213.23.130.223 (192.168.0.20[192.168.0.20]) - RootLogin 213.23.130.223 (192.168.0.20[192.168.0.20]) - RequireValidShell 213.23.130.223 (192.168.0.20[192.168.0.20]) - CURRENT-CLIENTS 213.23.130.223 (192.168.0.20[192.168.0.20]) - USER 213.23.130.223 (192.168.0.20[192.168.0.20]) - USER xxxxxx: Login successful. 213.23.130.223 (192.168.0.20[192.168.0.20]) - Preparing to chroot() the environment, path = '' 213.23.130.223 (192.168.0.20[192.168.0.20]) - Environment successfully chroot()ed. 213.23.130.223 (192.168.0.20[192.168.0.20]) - unable to chdir to /xxxxxx (No such file or directory), defaulting to chroot directory 213.23.130.223 (192.168.0.20[192.168.0.20]) - in dir_check_full(): path = '/', fullpath = '/'. 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching POST_CMD command 'PASS (hidden)' to mod_cap 213.23.130.223 (192.168.0.20[192.168.0.20]) - mod_cap/1.0: capabilities '= cap_chown,cap_net_bind_service+ep' 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching POST_CMD command 'PASS (hidden)' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching POST_CMD command 'PASS (hidden)' to mod_ls 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching POST_CMD command 'PASS (hidden)' to mod_auth 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'PASS (hidden)' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'PASS (hidden)' to mod_auth 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'SYST' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'SYST' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'SYST' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'SYST' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'FEAT' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'FEAT' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'FEAT' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'FEAT' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'CWD /' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'CWD /' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'CWD /' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - in dir_check_full(): path = '/', fullpath = '/'. 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'CWD /' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PWD' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PWD' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'PWD' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'PWD' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'TYPE A' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'TYPE A' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'TYPE A' to mod_xfer 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'TYPE A' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - Entering Passive Mode (213,23,130,223,17,37). 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'PASV' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'LIST' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'LIST' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'LIST' to mod_ls 213.23.130.223 (192.168.0.20[192.168.0.20]) - passive data connection opened - local : 213.23.130.223:4389 213.23.130.223 (192.168.0.20[192.168.0.20]) - passive data connection opened - remote : 192.168.0.20:4688 213.23.130.223 (192.168.0.20[192.168.0.20]) - in dir_check_full(): path = '/upload', fullpath = '/upload'. 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'LIST' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'LIST' to mod_ls 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'CWD upload' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'CWD upload' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'CWD upload' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - in dir_check_full(): path = '/upload', fullpath = '/upload'. 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'CWD upload' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PWD' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PWD' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'PWD' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'PWD' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - Entering Passive Mode (213,23,130,223,17,38). 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'PASV' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'LIST' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'LIST' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'LIST' to mod_ls 213.23.130.223 (192.168.0.20[192.168.0.20]) - passive data connection opened - local : 213.23.130.223:4390 213.23.130.223 (192.168.0.20[192.168.0.20]) - passive data connection opened - remote : 192.168.0.20:1031 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'LIST' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'LIST' to mod_ls 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'MKD test' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'MKD test' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'MKD test' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - in dir_check(): setting umask to 0002 (was 0002) 213.23.130.223 (192.168.0.20[192.168.0.20]) - chown(/upload/test) to gid 101 successful 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'MKD test' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - Entering Passive Mode (213,23,130,223,17,39). 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'PASV' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'LIST' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'LIST' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'LIST' to mod_ls 213.23.130.223 (192.168.0.20[192.168.0.20]) - passive data connection opened - local : 213.23.130.223:4391 213.23.130.223 (192.168.0.20[192.168.0.20]) - passive data connection opened - remote : 192.168.0.20:1074 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'LIST' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'LIST' to mod_ls 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'CWD test' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'CWD test' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'CWD test' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - in dir_check_full(): path = '/upload/test', fullpath = '/upload/test'. 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'CWD test' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PWD' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PWD' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'PWD' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'PWD' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - Entering Passive Mode (213,23,130,223,17,40). 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'PASV' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'LIST' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'LIST' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'LIST' to mod_ls 213.23.130.223 (192.168.0.20[192.168.0.20]) - passive data connection opened - local : 213.23.130.223:4392 213.23.130.223 (192.168.0.20[192.168.0.20]) - passive data connection opened - remote : 192.168.0.20:1075 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'LIST' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'LIST' to mod_ls 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'TYPE I' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'TYPE I' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'TYPE I' to mod_xfer 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'TYPE I' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - Entering Passive Mode (213,23,130,223,17,41). 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'PASV' to mod_log -------------------------------------------------------------------------------------- .: Hier ist der Teil über den erfolgreich abgeschlossenen Upload dokumentiert!!! 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'STOR testdatei' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'STOR testdatei' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'STOR testdatei' to mod_xfer 213.23.130.223 (192.168.0.20[192.168.0.20]) - in dir_check(): setting umask to 0002 (was 0002) 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'STOR testdatei' to mod_xfer 213.23.130.223 (192.168.0.20[192.168.0.20]) - chown(/upload/test/testdatei) to gid 101 successful 213.23.130.223 (192.168.0.20[192.168.0.20]) - passive data connection opened - local : 213.23.130.223:4393 213.23.130.223 (192.168.0.20[192.168.0.20]) - passive data connection opened - remote : 192.168.0.20:1165 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'STOR testdatei' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'STOR testdatei' to mod_xfer 213.23.130.223 (192.168.0.20[192.168.0.20]) - Transfer completed: 32978432 bytes in 4.28 seconds -------------------------------------------------------------------------------------- 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'TYPE A' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'TYPE A' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'TYPE A' to mod_xfer 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'TYPE A' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'PASV' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - Entering Passive Mode (213,23,130,223,17,42). 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'PASV' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'LIST' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'LIST' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'LIST' to mod_ls 213.23.130.223 (192.168.0.20[192.168.0.20]) - passive data connection opened - local : 213.23.130.223:4394 213.23.130.223 (192.168.0.20[192.168.0.20]) - passive data connection opened - remote : 192.168.0.20:1196 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'LIST' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching LOG_CMD command 'LIST' to mod_ls 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'QUIT' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'QUIT' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching PRE_CMD command 'QUIT' to mod_log 213.23.130.223 (192.168.0.20[192.168.0.20]) - dispatching CMD command 'QUIT' to mod_core 213.23.130.223 (192.168.0.20[192.168.0.20]) - FTP session closed. Wie kann ich es nun realisieren, daß abgebrochene Uploads nun doch automatisch vom Server gelöscht werden? Titel: Löschen abgebrochener Uploads Beitrag von: Wörsty am 23. Oktober 2003, 20:45:54 Ich sehe keinen Abbruch.
Titel: Löschen abgebrochener Uploads Beitrag von: NickTheRipper am 23. Oktober 2003, 20:58:00 Dank Dir für die schnelle Antwort!
Genau, das ist ja auch mir schleierhaft, denn ProFTPD erkennt den Abbruch nicht als diesen, sondern ist der Meinung es handelt sich um einen komplett abgeschlossenen Upload, obwohl dieser abgebrochen wurde. Ich habe die Testdatei einfach hochgeladen und beim hochladen habe ich auf "abbruch" geklickt und diesen Abruch des Uploads hätte meiner Meinung nach ProFTPD erkennen müssen, oder sehe ich das falsch? Titel: Löschen abgebrochener Uploads Beitrag von: stonki am 24. Oktober 2003, 08:47:31 Zitat von: "NickTheRipper" Dank Dir für die schnelle Antwort! Ich habe die Testdatei einfach hochgeladen und beim hochladen habe ich auf "abbruch" geklickt und diesen Abruch des Uploads hätte meiner Meinung nach ProFTPD erkennen müssen, oder sehe ich das falsch? hmm, uploade einmal und kille den Upload Prozess mittels (kill -9) oder eben unter Windows. Kann ja sein, dass "Abbrechen" beim Client sich noch schön beendet. ProFTPD kann ja _nicht_ wissen, wie gross die Datei sein soll. cu stonki Titel: Löschen abgebrochener Uploads Beitrag von: Wörsty am 24. Oktober 2003, 09:00:47 Zitat von: "stonki" kille den Upload Prozess mittels (kill -9) oder eben unter Windows. Nur damit du uns richtig verstehst... Den FTP-Client killen - nicht proftpd! Titel: Löschen abgebrochener Uploads Beitrag von: NickTheRipper am 24. Oktober 2003, 17:20:39 Ich hab Euren Tip befolgt und den FTP-Clienten unter Windows einfach zur Strecke gebracht, aber ProFTPD ist weiterhin der Meinung der Upload wäre vollständig.
Als Dateigröße zeigt er korrekterweise die Größe des bereits raufgeladenen Files an, aber ProFTPD ist der Meinung das dies korrekt ist und wertet dies im Debug als "Transfer completed" aus. Als ProFTPD läuft der aktuelle (V1.2.9RC3). Den Befehl "DeleteAbortedStores on" kann man ja in verschidenen Sektionen einbinden, aber jegliche Versuche sind gescheitert. Der abgebrochene Upload wird immer als "Transfer completed" ausgewertet. Titel: Löschen abgebrochener Uploads Beitrag von: stonki am 24. Oktober 2003, 18:57:16 Zitat von: "NickTheRipper" Als ProFTPD läuft der aktuelle (V1.2.9RC3). Den Befehl "DeleteAbortedStores on" kann man ja in verschidenen Sektionen einbinden, aber jegliche Versuche sind gescheitert. Der abgebrochene Upload wird immer als "Transfer completed" ausgewertet. ist nen Bug, kann ich bei mir nachvollziehen. Du siehst, das im transferlog auch (C) für Complete steht. cu stonki Titel: Löschen abgebrochener Uploads Beitrag von: Wörsty am 24. Oktober 2003, 20:17:06 Wer schreibt den BUG-Report :arrow: http://bugs.proftpd.org/ :?:
Ich. http://bugs.proftpd.org/show_bug.cgi?id=2254 Titel: Löschen abgebrochener Uploads Beitrag von: Wörsty am 24. Oktober 2003, 20:45:17 Habe das gerade nochmal getestet.
Bei mir geht's, wenn ich den Client kille. Wenn ich ABORT benutze, klappt es nicht. Version: 1.2.9rc3 (devel) Titel: Löschen abgebrochener Uploads Beitrag von: Wörsty am 24. Oktober 2003, 21:38:04 Na toll. Nun haben wir 2 Bugreports :roll: :arrow: 2253 (http://bugs.proftpd.org/show_bug.cgi?id=2253) und 2254 (http://bugs.proftpd.org/show_bug.cgi?id=2254)
Titel: Löschen abgebrochener Uploads Beitrag von: stonki am 25. Oktober 2003, 10:05:33 Zitat von: "Wörsty" Na toll. Nun haben wir 2 Bugreports :roll: :arrow: 2253 (http://bugs.proftpd.org/show_bug.cgi?id=2253) und 2254 (http://bugs.proftpd.org/show_bug.cgi?id=2254) http://bugs.proftpd.org/show_bug.cgi?id=1541 das ist der richtige und es gibt wenig Hoffnung :( cu stonki Titel: Löschen abgebrochener Uploads Beitrag von: Wörsty am 25. Oktober 2003, 10:30:06 Bei mir kommt gar kein ABOR...
Upps. Naja. :? Titel: Löschen abgebrochener Uploads Beitrag von: NickTheRipper am 27. Oktober 2003, 16:29:16 Ich danke Euch für die schnelle Erstellung eines Bugreports! Ist es nun eigentlich ein Problem von ProFTPD, oder ein Problem des verwendeten FTP-Clienten, der eventuell den "ABORT" - Befehl nicht ordnungsgemäß an ProFTPD übergibt, dies ist für mich aus den beiden erstellten und weiter dokumentierten Bugreports nicht richtig ersichtlich?
Titel: Löschen abgebrochener Uploads Beitrag von: stonki am 27. Oktober 2003, 18:12:00 Zitat von: "NickTheRipper" Ich danke Euch für die schnelle Erstellung eines Bugreports! Ist es nun eigentlich ein Problem von ProFTPD, oder ein Problem des verwendeten FTP-Clienten, der eventuell den "ABORT" - Befehl nicht ordnungsgemäß an ProFTPD übergibt, dies ist für mich aus den beiden erstellten und weiter dokumentierten Bugreports nicht richtig ersichtlich? also so wie ich das verstanden habe, ein Problem des Clients und nicht vom Server... cu stonki Titel: Löschen abgebrochener Uploads Beitrag von: Wörsty am 27. Oktober 2003, 19:19:39 :dito)
|