Hi,
I'm running VisualCron version 9.7.5. The touch file task, creates a file (if the file does not exist).
Example. In the task, touch file, I set the file pattern to happy.txt. I'm checking the directory c:\docs. The happy.txt file does not exist in the c:\docs directory. When the task runs, it creates the happy.txt file. This was not the behaviour in version 9.3.0. In version 9.3.0, a file is not created. Is this the expected behaviour in version 9.7.5?

Michael,

I think it is meant to do that...
In the Linux world when using the touch command it also creates the file.

What you could do is first list all files in the dir, than when happy.txt exists touch it, if not than exit.

It does that for me too (since at least v9.6.5) but I find it hard to accept the statement "it is supposed to do that"...It did not do that before

It does that for me too (since at least v9.6.5) but I find it hard to accept the statement "it is supposed to do that"...It did not do that before

https://www.geeksforgeek...-in-linux-with-examples/ 

This is directly taken from the linux command.

---

It does that for me too (since at least v9.6.5) but I find it hard to accept the statement "it is supposed to do that"...It did not do that before

You're right - a bug that now has been fixed.

---

Michael,

I think it is meant to do that...
In the Linux world when using the touch command it also creates the file.

What you could do is first list all files in the dir, than when happy.txt exists touch it, if not than exit.

Thanks for the feedback.

My question was, "in previous versions it did not do this...but does it now...is this the expected result".

The answer is, "this is the expected result".

Michael,

I think it is meant to do that...
In the Linux world when using the touch command it also creates the file.

What you could do is first list all files in the dir, than when happy.txt exists touch it, if not than exit.

It would be helpful for these type of changes in behaviour or "bug fixes" be listed in the release notes. I dont recall seeing anything mentioned about a change in the "touch files" task. Which is another reason why I posted the question. Yeah, seems obvious right?

Michael,

I think it is meant to do that...
In the Linux world when using the touch command it also creates the file.

What you could do is first list all files in the dir, than when happy.txt exists touch it, if not than exit.

It would be helpful for these type of changes in behaviour or "bug fixes" be listed in the release notes. I dont recall seeing anything mentioned about a change in the "touch files" task. Which is another reason why I posted the question. Yeah, seems obvious right?

I understand that. We are working on improving it on our end to make sure you get every single detail and change in the changelog. In rare cases it can happen so that a rather unknown bug/wrongful behaviour can be fixed in a change done somewhere else without us noticing if it for some reason slips past our test procedure. Could have been the case here, i'm not entirely sure.

---

Michael,

I think it is meant to do that...
In the Linux world when using the touch command it also creates the file.

What you could do is first list all files in the dir, than when happy.txt exists touch it, if not than exit.

It would be helpful for these type of changes in behaviour or "bug fixes" be listed in the release notes. I dont recall seeing anything mentioned about a change in the "touch files" task. Which is another reason why I posted the question. Yeah, seems obvious right?

Hi, michaelhum, this was written in the changelog of version 9.3.5
https://www.visualcron.com/changelog.aspx 

[BUGFIX] Server: Touch file Task->Fixed issue not creating files if file was not found (VC-1526)