You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since on Unix platforms Path::Class::File::copy_to uses system() to run cp handling (or even logging) copy errors is impossible in my daemon: The cp writes it's error messages to a stderr that has been closed long ago...
The text was updated successfully, but these errors were encountered:
wagnerflo
changed the title
Can't handle errors for copy_to on Unix
Can't handle errors for copy_to on Unix
Dec 12, 2018
Thanks for the report. My assumption is that the system cp performs better than the Perl emulation in File::Copy::cp, and handles permissions cases better, but I haven't really verified any of that. I agree that it makes error checking more difficult (the caller doesn't know whether it should check $? or $@ or $! or what).
Would using File::Copy::cp work better in your use case, and if so, do you know a performance comparison?
Since on Unix platforms
Path::Class::File::copy_to
usessystem()
to runcp
handling (or even logging) copy errors is impossible in my daemon: Thecp
writes it's error messages to a stderr that has been closed long ago...The text was updated successfully, but these errors were encountered: