found the same behavior using smbget with errornous parameters. Maybe it
should do so: return not the error code but the count of files it got?
Although that would be really strange...
cu jth
No, its just that the exit status is reversed from the standard.
Successful completion should return
smbget -Rr smb://localhost/share
[all files and folders are copied successfully!]
echo $?
1
On the other hand, when smbget is introduced with an error
smbget -Rr smb://localhost/shar
Can't open directory smb://localhost/shar: No such file or directory
echo $?
0
This is breaking my error
