If a remote share mounted locally goes off-line, Dolphin becomes very slow when navigating the local machine.
Any ideas please?
If a remote share mounted locally goes off-line, Dolphin becomes very slow when navigating the local machine.
Any ideas please?
Really surprised that no-one else has experienced this!!
What do you mean with this?
What “remote share”?
How “mounted locally”?
How "going off-line?
Opensuse 15.5
Dolphin 22.12.3
Plasma 5.274.9
Wired LAN
Shares (SAMBA) are mounted in fstab thus:
//remotemachine/share /mnt/localmount cifs
By “going off-line” I mean if the remote machine is powered off.
OK, thus it is about SAMBA. I never use(d) it (not doing anything Windows), thus I assume you have to wait for the SAMBA gurus.
But I assume that when you travel around with Dolphin it tries every time and waits for a time-out.
Thanks. What might you suggest as an alternative (I am no longer using any Windows machines, my whole network is Linux).
Including the file server?
Unix/Linux has NFS since long before SAMBA.
But I will not promise that breaking the connection to a file server will not have negative consequences.
There is no main server as such, just peer to peer (it’s a home network).
A server (of any kind) in Unix/Linux parlance is a function, some running software (daemon) that offers a service over the TCP/IP network. So whenever you have a file server that can easily be run on a system that has more functionality, like print server, workstation, x_server, …
So, I understand that your server is also on a Linux system.
For me it is very strange that one uses a protocol/software that is designed to provide file serving from a Unix system to Windows clients (more stable in those days then MicroSofts own solution) and later added file client features (so that Unix systems could use corporate MS file servers in a mostly MS oriented shop) as a file client/server solution in a purely Unix/Linux environment.
Whenever dolphin gets slow terminate the running instance. dolphin --new-window /home
makes dolphin fast again.
So, what would you suggest? NFS? My understanding of that is that it does not allow username and password authentication - if so, that makes it a no-go.
@KermitXYZ Since ssh is usually running, just use sftp or sshfs?
mkdir test_sshfs
sshfs remote:/home/username ~/test_sshfs
umount ~/test_sshfs
If on a windows machine I use winscp…
I have no idea what you mean with this. But as NFS is a Unix/Linux solution, it works like all files vs. UID and GID and permissions. There is no difference with respect to ownership and permissions between a file on a local mounted file system or one that is remote/NFS mounted. Nobody should see any difference.
Thus it is of importance that amongst server and clients the user and group administration should be centralized. Else a file that is owned by UID 1000 with username agnes
on systema
will be owned by UID 1000 (of course) with username bernard
on systemb
. Thus there must be one pool of users where e.g. UID 1000 is agnes
and UID 1001 is bernard
on all systems.