AW: Troubles with wput-0.4w32

["Alexander Hass" <alexander.hass@e-domizil.de>]

Sorry - war wohl auch etwas meine Ungedult schuld. Allerdings ist es auch etwas krass wie lange es dauert. Hier kam nämlich doch noch etwas... aber es hat 5minuten gedauert! Woran kann das liegen?

Directory-Listing:
-rw-r--r--   1 web1     ftponly         0 Oct 14 19:57 pc_ie_neu.css

-----
PLAINFILE; month: Oct; day: 14; time: 19:57:0 (no yr);
timestamping: local: 1083673393 seconds; remote 1097776615 seconds; diff: 18446744073695448394
-- Skipping file: .\pc_ie_neu.css (remote is newer)
---->QUIT
221 Goodbye.



-----Ursprüngliche Nachricht-----
Von: Alexander Hass 
Gesendet: Freitag, 15. Oktober 2004 09:57
An: 'headshot@itooktheredpill.dyndns.org'
Betreff: AW: Troubles with wput-0.4w32


Hallo Hagen

Habe garnicht gesehen, dass es auch in deutsch geht. In der Anlage mal die Debug Ausgabe. Gibt es einen Zeitplan für die 0.5w32 ? Ich brauche das Tool eigentlich ziemlich dringend und ich weiss echt nicht was man alternativ nutzen soll.

Was ist denn eigentlich das wputrc File? Gelesen habe ich davon, aber details was man damit machen kann vermisse ich im Manual.
 

Mit freundlichen Grüßen
Alexander Hass


-----Ursprüngliche Nachricht-----
Von: Hagen Fritsch [mailto:hagen@itooktheredpill.dyndns.org] 
Gesendet: Freitag, 15. Oktober 2004 08:44
An: Alexander Hass
Betreff: Re: Troubles with wput-0.4w32


I'm currently rewriting wput, so 0.5 will be different a little more 
user-friendly esp. concerning error-messages. When creating a 
data-connection, wput tries either passive-mode or if specified by 
command-line port-mode. If either one fails creating a connection, wput will 
automatically try the other one and remember the setting.
In your case wput is using passive mode and the connection is established, but 
it seems as though the LIST command never finishes.
You could try to turn debug-mode (-d flag) on and maybe you'll see some 
error-messages.
The timestamping feature in wput < 0.5 does not work correctly since 
ftp-servers usually issue UTC-time whereas wput uses the local-time instead, 
so you might need to set the timestamping-concerning options in a wputrc 
file.
Regards,
Hagen

Am Donnerstag, 14. Oktober 2004 22:12 schrieben Sie:
> Dear Hagen
>
> i've got troubles get wput running. are you able to help with the
> following problems? i'm uploading files from a network/local path to a 
> external ftp server. firewall only allows passive transfer.
>
> Problems:
> 1. it is not possible to specify full paths for uploading. for e.g.
> "wput I:\dir1\css ftp://user1:password1@server1.server.de/html/css/";. 
> this result on the ftp server as 
> ftp://user1:password1@server1.server.de/html/css/I:/dir/css and is 
> wrong as you see... switching with cd to all dirs required for upload 
> is very error prone...
>
> 2. i'd ike to use --timestamping. from my understanding the file on
> the target ftp server will have the local file time set after 
> transfer. isn't it? if i'm using this option i'm unable to transfer 
> anything wput stops at:
>
> I:>P:\Utilities\FTP\wput\wput -v --timestamping pc_ie.css
> ftp://user1:password1@server1.sserver.de/html/css/ --22:04:57-- `pc_ie.css'
>     => ftp://user1:xxxxx@1.1.1.1/html/css/pc_ie.css
> Connecting to 1.1.1.1:21...  connected!
> Logging in as user1 ... Logged in!
> ==> CWD /html/css/ done.
> ==> PASV done.
> ==> TYPE A ... done
> ==> LIST ... done.
>
> maybe wput is using active in this situation and is blocked by
> firewall!? i don't understand the command option --port-mode and the 
> syntax for forcing it to passive mode.
>
>
> Regards
> Alexander Hass

-- 
Mit besten Grüßen
 Hagen                          mailto:itooktheredpill@gmx.de
                      http://itooktheredpill.dyndns.org