NOTICE: .zoom/data/com.zoom.ipc.assistantapp__res: Can't transfer non file/directory
NOTICE: .zoom/data/com.zoom.ipc.assistantapp__req: Can't transfer non file/directory
The items show as type 'pipe' in my graphical file manager. In a terminal:
$ ls -all
[. . .]
prw------- 1 [. .] 0 Dec 26 00:05 com.zoom.ipc.assistantapp__req
prw------- 1 [. .] 0 Dec 25 18:01 com.zoom.ipc.assistantapp__res
Is there a way, please, of telling rclone to exclude this type of item? Ah, I see that there is 'metadata filtering' (Rclone Filtering) . .
Run the command 'rclone version' and share the full output of the command.
These don't cause an error in the sync, just a log message. Untidy but the sync is still good
I think this log message comes before the filtering so you can't exclude it with a metadata filter yet, but nice idea.
Rclone should allow these files through when using -M syncs most likely then you could backup and restore device nodes etc. Not sure you can ever backup a pipe or a socket though?
I ill understand the following, partly because the first sentence (being ungrammatical) is hard to parse.
Rclone should allow these files through when using -M syncs most likely then you could backup and restore device nodes etc. Not sure you can ever backup a pipe or a socket though?
Sorry! Although English is my first language, I don't seem to be able to speak it any more Here is my second attempt:
Rclone should allow devices, pipes and sockets to appear in listings (rather than give the error above) when using -M. This would mean syncs could transfer them and re-create them in the destination. I'm unsure whether you can sensibly back up pipes and sockets though.
Here's the thing though. I suppose that I could use -M to backup the 'pipes' but I think that I'd rather leave them alone whilst suppressing the 'notices' that rclone generates when (having been run without -M) it encounters such items. I take it that at present there is a way to do that, but not a fine-grained one - that sledgehammer-y way being to lower rclone's log-level.
I copied this behaviour from rsync which moans about stuff it can't transfer and expects you exclude it.
Except:
I think this log message comes before the filtering so you can't exclude it with a metadata filter yet, but nice idea.
I think that implementing the 'nice idea', and thereby being more rsync-y, would be the way to go. Still, I'd take either of your other options (viz.: a way of telling rclone to be quiet about, specifically, pipes.; and not reporting transferred pipes at log-level 'notice').