-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Not all remote shares removed #13569
Comments
@schiesbn |
@PVince81 handled by your PR to catch exceptions in s2s? THX |
Possibly. Note that some shares only auto-delete when navigating into them (whenever something tries to find out whether they were updated). If the sync client runs once on them they should all disappear. PR is here, need to try out: #13525 |
This works as described by PVince81 for folders. |
The problem with the background job approach is that it will ping the remote server with a regular interval, which might not be desirable (especially when many users have lots of shares). On the other hand, it could be used as a general process to detect unavailable/obsolete remote storages (a bit like @Xenopathic's work) |
ref: #13641 |
@PVince81 8.2 I assume? THX |
Yes, let's move it to 8.2 |
Hey, this issue has been closed because the label (This is an automated comment from GitMate.io.) |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Steps to reproduce
Expected behaviour
All shares removed from system one
Actual behaviour
Some shares remain.
Server Host info:
Ubuntu 14.04
PHP 5.5.9
Log file
Server configuration
ownCloud Enterprise Edition 8.0 beta 1 (daily) Build:2015-01-21T04:13:37+00:00
The text was updated successfully, but these errors were encountered: