Symlink files lead to errors
See original GitHub issueHello @xeraph
2.6.0 tested on Debian 11 symlinks lead to errors:
Error: File not found. Skipping /etc/sv/ssh/supervise
Tested with and without --no-symlink
Thank you for your work!
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Symbolic Links (Symlinks) Produce Errors - Oracle Help Center
Symbolic link targets that work on one client might be broken on another due to differences in file system layout or because clients...
Read more >How to fix: The symbolic link cannot be followed because its ...
Remote to remote symbolic links are disabled . In order to enable remote to remote symbolic links, enter the following command: C:\>fsutil ...
Read more >Symlink Error: PHP Warning: symlink(): File exists
It seems like the error was caused in the public_html folder that already contained an "images" folder. After removing the images folder ...
Read more >[MS-SMB2]: Symbolic Link Error Response - Microsoft Learn
The Symbolic Link Error Response is used to indicate that a symbolic link was encountered on create; it describes the target path that...
Read more >What is a "failed to create a symbolic link: file exists" error?
Use ln -sf instead of ln -s . Be careful though, as this may overwrite your original file with a broken symlink. Check...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hello @xeraph
first I want to wish you a merry xmas!
I meant the native image files. Especially the linux binary, as we need to deploy them on many hosts. But if it is not possible to shrink them, we will surely live with that.
Thanks again for your work here.
Maybe same approach for symlink can be good alternative… (error report for explicitly specified paths)