-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid deleting the collective-folder with dcs #1659
Comments
Hi @qdrop17 hm, that sounds not so good :-) Do you mean that dsc deletes even the collective directories, like The former would be a bug I think. The latter is currently on purpose to not leave empty directories around. But we can add a flag to keep empty directories when deleting files. I think currently to avioid this, you could play with directory permissions such that dsc cannot delete them (and live with the errors in the logs). Or you could remove the |
Hi @eikek yeah, I mean that the collective folder I tried to limit the permissions, but this leads to an issue, that it would not complete an import and therefore wouldn't continue to poll. I currently disabled the "--delete" feature and I have another cronjob that does the cleanup. |
That is really a strange bug, I cannot see this behavior on my installation (but I don't use |
Let me know what I can do to help you reproduce this issue. What's important: The docs-volume is a cifs mount into the container. That's why I can't use "--watch" as cifs-mounts don't offer inotify. |
Thank you! I'll come back to it if necessary. Just on a general note, if you haven't considered it yet: you could run the dsc process on the other machine (that exports the cifs), too. Then you could use |
First of all: Awesome software! I highly appreciate it.
I have a very small issue that I don't manage to resolve:
I mounted a cifs directory into my dsc container, enabling it to fetch new scanned documents from my NAS. This works flawlessly. Unfortunately, the "--delete"-flag not only deletes the imported pdf-files but the collective directories (inside /opt/docs/[collective]) too. This is quite problematic as my scanner is sending the scans there. This will fail if the directory is not existent.
How can this behaviour be avoided?
The text was updated successfully, but these errors were encountered: