Team C
[ZBX-13117] Junctions and symlinks are not properly handled by vfs.dir.size on Windows Created: 2017 Nov 30 Updated: 2024 Apr 10 Resolved: 2018 Feb 05 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Agent (G) |
| Affects Version/s: | 3.4.4 |
| Fix Version/s: | 3.4.7rc1, 4.0.0alpha3, 4.0 (plan) |
| Type: | Incident report | Priority: | Trivial |
| Reporter: | Andris Zeila | Assignee: | Michael Veksler |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Team: | Team C |
| Team: | Team C |
| Sprint: | Sprint 23, Sprint 24, Sprint 25, Sprint 26 |
| Story Points: | 1 |
| Description |
|
Create two directories which contains symlinks or junctions (created with mklink) to each other. While apparently there are some safeguards (or just luck?) in Windows and it will not result in infinite recursion, it does loop 70+ times and gives incorrect result. On *nix systems symlinks are followed only once. However that is done by checking inode, not sure if we can apply similar pattern on Windows. In worst case it would be better to ignore symlinks/juctions on Windows and document it. |
| Comments |
| Comment by Michael Veksler [ 2018 Jan 23 ] |
|
Available in pre-4.0.0alpha3 (trunk) r77115 |
| Comment by Michael Veksler [ 2018 Jan 24 ] |
|
Available for testing version |