diff options
| author | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2011-11-06 02:23:21 -0600 |
|---|---|---|
| committer | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2011-11-06 02:23:21 -0600 |
| commit | b1c6ea23c4e7f1939dcade2b86c31c864a2e4e6b (patch) | |
| tree | 67db2e50a264645d1991043917e1d1c91da30d2b /FAQ | |
| parent | b30f13d4c850f51159dc701d0e390657486e9fcb (diff) | |
| download | smb4k-b1c6ea23c4e7f1939dcade2b86c31c864a2e4e6b.tar.gz smb4k-b1c6ea23c4e7f1939dcade2b86c31c864a2e4e6b.zip | |
Additional kde to tde renaming
Diffstat (limited to 'FAQ')
| -rw-r--r-- | FAQ | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -272,13 +272,13 @@ A: First of all, check that you haven't opened the mount point or one of its haven't opened any file belonging to the share. If neither is the case, you might have encountered a problem, that is known but not related to Smb4K. It seems, that under certain circumstances (that we could not - figure out exactly) kdeinit (KDE < 3.4) background processes access files + figure out exactly) tdeinit (KDE < 3.4) background processes access files and/or directories of the share and keep them open. Unmounting is not possible unless you send $ kill -HUP <PID> - to each kdeinit instance that has access to the share or its files. + to each tdeinit instance that has access to the share or its files. Alternatively, you can force the unmounting of the share. Highlight the share and use the Shares->Force Unmounting menu item or press Ctrl+F. |