Hello Robert,

Yes, see attached picture. Are you seeing something different?

WF does trigger the actions.

However (maybe this is what you were seeing), there is some code inside WF that will deliberately ignore timestamp changes in certain situations. I will have to check on that.

When you look at the "changes since" window, do you see the existingfile.tst as a changed file?

Can you right-click the task and select "backup", please email me the zip this creates.
You may want to change the user/pass in its settings first.

Gert wrote on Jan 31^st, 2014, 7:51am:


Gert,

OK then...what if the "touch" changes ALL 3:


[robert:~/xmldir]$uname -a
SunOS secdpdevdb01 5.10 Generic_144488-11 sun4v sparc SUNW,Sun-Blade-T6300

[robert:~/xmldir]$truss -v lstat -t lstat ls -l existingfile.tst
lstat64("existingfile.tst", 0xFFBFF718)         = 0
   d=0x04B40000 i=6485896 m=0100644 l=1  u=1133  g=600   sz=0
       at = Jan 30 11:23:25 EST 2014  [ 1391099005.118259000 ]
       mt = Jan 30 11:23:25 EST 2014  [ 1391099005.118259000 ]
       ct = Jan 30 11:23:25 EST 2014  [ 1391099005.118270000 ]
   bsz=8192  blks=0     fs=ufs
-rw-r--r--   1 robert    acusers       0 Jan 30 11:23 existingfile.tst

[robert:~/xmldir]$touch existingfile.tst

[robert:~/xmldir]$truss -v lstat -t lstat ls -l existingfile.tst
lstat64("existingfile.tst", 0xFFBFF798)         = 0
   d=0x04B40000 i=6485896 m=0100644 l=1  u=1133  g=600   sz=0
       at = Feb  1 02:46:21 EST 2014  [ 1391240781.811244000 ]
       mt = Feb  1 02:46:21 EST 2014  [ 1391240781.811244000 ]
       ct = Feb  1 02:46:21 EST 2014  [ 1391240781.811254000 ]
   bsz=8192  blks=0     fs=ufs
-rw-r--r--   1 robert    acusers       0 Feb  1 02:46 existingfile.tst



History: I have done several "touch existingfile.tst" during this:



Changed since:




Are you not able to reproduce what I'm observing ?

I mean are you actually seeing that each of YOUR "touch existingfile.tst" between each scans trigger the action ?

By the way, WF has a setting somewhere "ignore zero byte files", perhaps that option is "on" for your task?

WF 3.5 (and higher) does not compare timestamps to a local file. That was the big change for 3.5. It maintains a little db with timestamps and sizes of files and compares to that.

In my previous post I just mentioned "download" because that is what my standard test task does. It should work fine in your case when you do not download.

Please try the link to the beta I posted earlier, that was the version I used with my test.

the history.db is sqlite.

The timestamps/sizes are inside ftpdirlist_yyyymmdd.watchftp files inside the task directory. Plain txt, but please do not try to change them, the format is a little special and it may cause aborts. The changes since window basically shows the diff of 2 of those files.

Just install "on top" of your current install and all settings/tasks will work fine.

I have created a new task based on your settings. The only special thing I saw with your settings is that you use SFTP. SFTP and FTP are 2 totally different protocols, even if they share the "ftp" in their name, they work totally different.

Created the task, let it do an initial scan (so all current file sizes and timestamps are recorded without taking action), used FileZilla again to download/re-upload a file so its timestamps are touched.

The file was detected by WF and my bat file triggered. What you can try, on the FTP Server Settings tab, is check the option "keep session log". This will record all activity in a yyyymmdd.log file (or right-click the task and "view session log"). Run the task and (after touching existingfile.txt) open the log. Search for all occurrences of existingfile.txt and you should some filesize/timestamp info for the file.

For example, I "touched" the file "dfsgsddfz- kopie.txt", and see the following in the log:

20140202 064253 ** found file dfsgsddfz- kopie.txt
20140202 064253              Size 5005
20140202 064253        Last Modif 30-8-2012 11:47:08
20140202 064253           Created 30-8-2012 11:47:08
...
20140202 064723 ** found file dfsgsddfz- kopie.txt
20140202 064723              Size 5005
20140202 064723        Last Modif 2-2-2014 6:46:57
20140202 064723           Created 2-2-2014 6:46:57

and my bat file triggered fine. I now see the logging code doesn't log the fact it will trigger actions in this case, I will add that to the code.

My bat script is really simple, it just echos all environment variables:
Code:

SET WF_ > f:\testing\output.log
 

and after running the task, this is what I see in my output.log file
Code:

WF_AGECREATED_DAYS=
WF_AGECREATED_HOURS=
WF_AGEMODIFIED_DAYS=
WF_AGEMODIFIED_HOURS=
WF_CONFIG=RCTEST
WF_CUREVT=1391320042
WF_CURRUN=1
WF_DATE=20140202
WF_DIR=
WF_DTTM=20140202 064752
WF_FILE=C:\TaskDoesntDownload\home\watchdir\WATCHFTPTESTS\dfsgsddfz- kopie.txt
WF_FILE_B=dfsgsddfz- kopie
WF_FILE_D=C:\TaskDoesntDownload\home\watchdir\WATCHFTPTESTS\
WF_FILE_DATE_CR=
WF_FILE_DATE_LM=
WF_FILE_E=TXT
WF_FILE_LOCAL=C:\TaskDoesntDownload\home\watchdir\WATCHFTPTESTS\dfsgsddfz- kopie.txt
WF_FILE_N=dfsgsddfz- kopie.txt
WF_FILE_REMOTE=/home/watchdir/WATCHFTPTESTS/dfsgsddfz- kopie.txt
WF_FILE_SHORTNAME=
WF_FILE_SHORTPATH=
WF_FILE_SIZE=
WF_FILE_SIZE_KB=
WF_FILE_TIME_CR=
WF_FILE_TIME_LM=
WF_FIRSTDIR=:
WF_INSTDIR=C:\Program Files\WatchFTP
WF_OFILE=
WF_OFILE_B=
WF_OFILE_D=
WF_OFILE_E=
WF_OFILE_N=
WF_ORELDIR=
WF_PARENTDIR=WATCHFTPTESTS
WF_REASON=FILENEW
WF_RELDIR=:\TaskDoesntDownload\home\watchdir\WATCHFTPTESTS
WF_TASK=RCTEST
WF_TASKDIR=C:\ProgramData\WatchFTP\RCTEST
WF_TIME=064752
 

Note that I asked you for a task backup earlier so I could properly look at your settings and recreate the task. Sorry to hear you don't appreciate 7-days per week service from the one person in my company that knows most about the working of our programs.

Thanks, will try it out

So "new files" in "Only download new files" means file(s) with non-existing name(s) ?

Gert

Question:
Can I use the 2nd Batch Script option "Run after multiple downloads" in my case where I do not want to download ?