scripted synchronize fails to properly follow local symlinks to PDF files, and *only* PDF files

I have WinSCP configured to synchronize several local directories to my server via FTP. The files on the server never change; only the local files and directories change (for now.) The local directories contain symlinks to various folders and files.

Everything works as expected *except* the way WinSCP resolves symlinks to local PDF files, and *only* PDF files.

The WinSCP log indicates that every time it checks a symlink that references a PDF file on my local machine, it thinks the file has changed (they have not...) and initiates a STOR rather than simply skipping over that PDF file.

When WinSCP checks symlinks to folders and other file types (.jpg, .doc, etc.) it syncs as expected; i.e. if the local file referenced by the symlink hasn't changed, WinSCP skips that file and does not initiate a STOR.

Here's my script:

/console /command "open ""hubHTML 10837""" "synchronize remote ""-filemask=|*h5ai;*.htaccess;*.TBD*/;*h5ai/"" -delete" "exit"

...and I've attached the log file. Note that the only files that get transferred are PDFs. Here is the full list of local files that are referenced via symlink:

10837 Basement K1tchen 09-24-11.jpg
10837 Basement Seattle DPD ADU Removal Modifications 04-2013.docx
10837 DOWNSTAIRS Renovation Budget.xls
10837 Electrical & Plumbing Summary Letter 06-22-05.doc
10837 Gas Piping Permit 11-07-12.pdf
10837 Maintenance.xlsx
10837 stove infill 04-2013 003.jpg
10837 stove infill 04-2013 006.jpg
10837 UPSTAIRS Remodel Expenses 02-25-06.xls
2003 10837 Assessment.pdf
2013-10 10837 Craigslist ad photo 001 k1tchen2.jpg
2013-10 10837 Craigslist ad photo 002 Sarah's K1tchen 07-06-05 001.jpg
2013-10 10837 Craigslist ad photo 003 bathroom3.jpg
2013-10 10837 Craigslist ad photo 004 garage1.jpg
2013-10 10837 Craigslist ad photo 005 livingroom5.jpg
2013-10 10837 Craigslist ad photo 006 rosepatio.jpg
2013-10 10837 Craigslist ad photo 007 3.jpg
2013-10 10837 Craigslist ad photo 008 4.jpg
2013-10 10837 Craigslist ad photo 009 laundry.jpg
2013-10 10837 Craigslist ad photo 010 10837 stove infill 04-2013 009.jpg
2013-10 10837 Craigslist ad photo 011 bathsink.jpg
2013-10 10837 Craigslist ad photo 012 10837 Annual Inspection 08-2007 017 (Large).jpg
A Portrait of Your Old House.doc
Correction Notice #1 11-30-11.pdf
Seattle House Research Resources.pdf
Seattle Parking Ticket 325360659 11-07-12.pdf




Thanks for any insights.



-----------------------
WinSCP 5.7.5
Windows 7 Pro

Thanks for your report.

I assume Seattle Parking Ticket 325360659 11-07-12.pdf is one of the problematic files, right?

I have sent you an email with a debug version of WinSCP to address you have used to register on this forum.

martin wrote:

I assume Seattle Parking Ticket 325360659 11-07-12.pdf is one of the problematic files, right?

Yes, that's correct. I'll download the debug version and set up a test scenario then report back with the logs.

Thanks

This issue has been added to the tracker:
https://winscp.net/tracker/1355

Thanks Martin-
Please let me know if I can assist with any additional testing. I suspect, as you do, that the issue is with the way some Windows APIs handle symlinks.

Hello again Martin-

FYI, I replaced my Windows file-symlinks with file-hardlinks and everything seems to be working fine now. Windows symlinks seem to work much better for folders than files; junction points also work well for folders. There have been several recent Windows Updates that have 'broken' Windows 7 symlink functionality, so I think using hardlinks whenever possible to link to files rather than symlinks is preferred.

Link Shell Extension is a great utility for creating and managing links in Windows.
https://schinagl.priv.at/nt/hardlinkshellext/hardlinkshellext.html

Thanks for sharing this.