Yes, I understood what you meant, but that is only 1 part of what I need
to do: I need to retrieve the files from the ftp server before I can
"touch" them, and that won't work either because of the leap year bug.
So I retrieve them with a manual ftp client, and then use a gui file
date/time c
I mean a cron job to touch the files and change the date
David kerber wrote:
The problem is that ftp.getfiles won't even retrieve the files from
the server! It sees them as invalid because of the date issue. So I
have to retrieve them manually. Yeah, I could script up that part as
well,
See
https://issues.apache.org/jira/browse/NET-190
https://issues.apache.org/jira/browse/NET-188
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EM
The problem is that ftp.getfiles won't even retrieve the files from the
server! It sees them as invalid because of the date issue. So I have
to retrieve them manually. Yeah, I could script up that part as well,
but I don't think it's worth it for now.
Adam Gordon wrote:
Dave-
Just set a
Dave-
Just set a cron job to do it every minute or (some other interval) and
then you don't have to worry about it - just don't forget to remove the
job tonight.
--adam
David kerber wrote:
Yeah, that's what I've done so far today, but the files come in
continuously throughout the day for a
Yeah, that's what I've done so far today, but the files come in
continuously throughout the day for a total of 1000 or so, and we need
to process them as they come in, so I've been letting them build up and
doing it every hour or so. It's a pain, and I hope they get this fixed
sometime before
Short of downloading/patching the source code and redeploying, just a
stab in the dark here, but maybe just execute "touch -d " in the
offending directory/directories. There's no recursive flag though,
bummer. At least it'll only be a problem for 12 more hours (MST).
HTH,
--adam
David kerb
I have found that the commons-net ftp.listfiles() fails to get files
whose date on the server is on feb 29. Googling indicates that this a
known problem (at least since this morning), but I haven't found a quick
fix. Does anybody know of one?
D
