You are not logged in.

#1 2018-12-08 09:31:41

squalou
Member
Registered: 2018-06-04
Posts: 112

[SOLVED] Access SMB mount point from shell,

Hi,
I'm using either XFCE or GNOME as DE.
Samba shares are mounted without issue from Thunar or Nautilus.

I used to access the mounted resources in this path :

/run/user/<my-user-id/gvfs/<some-path-name>

for something like a week, this path is no more populated.

And ... I can't find any other path where the share would be accessible.

This is very annoying for at least two practical reasons :

- 1 : shell access to files ! as simple as that
- 2 : open a folder on a shared resource from , for instance, your favorite web browser ... no way to find the path

Any advice welcome smile


Note : I've foud some thigns being populated here

~/.local/share/gvfs-metadata

but ... one kind of binary file and one log file... and that's all


kind regards

S.

Last edited by squalou (2018-12-08 17:29:10)

Offline

#2 2018-12-08 09:36:34

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: [SOLVED] Access SMB mount point from shell,

Can you find it from the output of...

findmnt

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#3 2018-12-08 17:14:13

squalou
Member
Registered: 2018-06-04
Posts: 112

Re: [SOLVED] Access SMB mount point from shell,

Nowhere to be found :-(

Here when a share is mounted : it's called 'books', it a local smb share on a nas on 182.168......

I don't even know by what magic it's accessible, does not look like a 'fuse' thing, but then, what could it be ?

TARGET                                SOURCE                              FSTYPE      OPTIONS
/                                     /dev/mapper/AntergosVG-AntergosRoot ext4        rw,relatime
├─/proc                               proc                                proc        rw,nosuid,nodev,noexec,relatime
│ └─/proc/sys/fs/binfmt_misc          systemd-1                           autofs      rw,relatime,fd=34,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=1775
│   └─/proc/sys/fs/binfmt_misc        binfmt_misc                         binfmt_misc rw,relatime
├─/sys                                sys                                 sysfs       rw,nosuid,nodev,noexec,relatime
│ ├─/sys/firmware/efi/efivars         efivarfs                            efivarfs    rw,nosuid,nodev,noexec,relatime
│ ├─/sys/kernel/security              securityfs                          securityfs  rw,nosuid,nodev,noexec,relatime
│ ├─/sys/fs/cgroup                    tmpfs                               tmpfs       ro,nosuid,nodev,noexec,mode=755
│ │ ├─/sys/fs/cgroup/unified          cgroup2                             cgroup2     rw,nosuid,nodev,noexec,relatime,nsdelegate
│ │ ├─/sys/fs/cgroup/systemd          cgroup                              cgroup      rw,nosuid,nodev,noexec,relatime,xattr,name=systemd
│ │ ├─/sys/fs/cgroup/cpu,cpuacct      cgroup                              cgroup      rw,nosuid,nodev,noexec,relatime,cpu,cpuacct
│ │ ├─/sys/fs/cgroup/hugetlb          cgroup                              cgroup      rw,nosuid,nodev,noexec,relatime,hugetlb
│ │ ├─/sys/fs/cgroup/pids             cgroup                              cgroup      rw,nosuid,nodev,noexec,relatime,pids
│ │ ├─/sys/fs/cgroup/rdma             cgroup                              cgroup      rw,nosuid,nodev,noexec,relatime,rdma
│ │ ├─/sys/fs/cgroup/net_cls,net_prio cgroup                              cgroup      rw,nosuid,nodev,noexec,relatime,net_cls,net_prio
│ │ ├─/sys/fs/cgroup/blkio            cgroup                              cgroup      rw,nosuid,nodev,noexec,relatime,blkio
│ │ ├─/sys/fs/cgroup/freezer          cgroup                              cgroup      rw,nosuid,nodev,noexec,relatime,freezer
│ │ ├─/sys/fs/cgroup/devices          cgroup                              cgroup      rw,nosuid,nodev,noexec,relatime,devices
│ │ ├─/sys/fs/cgroup/memory           cgroup                              cgroup      rw,nosuid,nodev,noexec,relatime,memory
│ │ ├─/sys/fs/cgroup/perf_event       cgroup                              cgroup      rw,nosuid,nodev,noexec,relatime,perf_event
│ │ └─/sys/fs/cgroup/cpuset           cgroup                              cgroup      rw,nosuid,nodev,noexec,relatime,cpuset
│ ├─/sys/fs/pstore                    pstore                              pstore      rw,nosuid,nodev,noexec,relatime
│ ├─/sys/fs/bpf                       bpf                                 bpf         rw,nosuid,nodev,noexec,relatime,mode=700
│ ├─/sys/kernel/debug                 debugfs                             debugfs     rw,relatime
│ │ └─/sys/kernel/debug/tracing       tracefs                             tracefs     rw,relatime
│ ├─/sys/kernel/config                configfs                            configfs    rw,relatime
│ └─/sys/fs/fuse/connections          fusectl                             fusectl     rw,relatime
├─/dev                                dev                                 devtmpfs    rw,nosuid,relatime,size=8060772k,nr_inodes=2015193,mode=755
│ ├─/dev/shm                          tmpfs                               tmpfs       rw,nosuid,nodev
│ ├─/dev/pts                          devpts                              devpts      rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000
│ ├─/dev/mqueue                       mqueue                              mqueue      rw,relatime
│ └─/dev/hugepages                    hugetlbfs                           hugetlbfs   rw,relatime,pagesize=2M
├─/run                                run                                 tmpfs       rw,nosuid,nodev,relatime,mode=755
│ └─/run/user/1000                    tmpfs                               tmpfs       rw,nosuid,nodev,relatime,size=1614648k,mode=700,uid=1000,gid=985
├─/boot                               /dev/nvme0n1p2                      ext4        rw,relatime,data=ordered
│ └─/boot/efi                         /dev/nvme0n1p1                      vfat        rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
└─/tmp                                tmpfs                               tmpfs       rw,nosuid,nodev

Offline

#4 2018-12-08 17:15:25

squalou
Member
Registered: 2018-06-04
Posts: 112

Re: [SOLVED] Access SMB mount point from shell,

I do have a gvfs-daemon.service running though

           │   │ ├─gvfs-daemon.service
           │   │ │ ├─ 1249 /usr/lib/gvfsd
           │   │ │ ├─ 4763 /usr/lib/gvfsd-trash --spawner :1.10 /org/gtk/gvfs/exec_spaw/0
           │   │ │ ├─ 4834 /usr/lib/gvfsd-network --spawner :1.10 /org/gtk/gvfs/exec_spaw/2
           │   │ │ ├─ 4853 /usr/lib/gvfsd-dnssd --spawner :1.10 /org/gtk/gvfs/exec_spaw/5
           │   │ │ ├─14150 /usr/lib/gvfsd-http --spawner :1.10 /org/gtk/gvfs/exec_spaw/11
           │   │ │ ├─26795 /usr/lib/gvfsd-smb --spawner :1.10 /org/gtk/gvfs/exec_spaw/20
           │   │ │ └─27313 /usr/lib/gvfsd-smb --spawner :1.10 /org/gtk/gvfs/exec_spaw/22

Offline

#5 2018-12-08 17:23:31

squalou
Member
Registered: 2018-06-04
Posts: 112

Re: [SOLVED] Access SMB mount point from shell,

If there's an alternative to gvfs-smb to mount easily smb shares, I'm not opposed to switch to it.

Offline

#6 2018-12-08 17:30:38

squalou
Member
Registered: 2018-06-04
Posts: 112

Re: [SOLVED] Access SMB mount point from shell,

Damn it.
I rebooted.
It works again.

Documentation here states that

The mounted share is likely to be present at /run/user/your_UID/gvfs in the filesystem.

I understand the 'likely' now smile

https://wiki.archlinux.org/index.php/Sa … nd_PCManFM

Offline

#7 2018-12-08 17:32:37

Stratoblaster
Member
From: Florida
Registered: 2018-12-04
Posts: 58

Re: [SOLVED] Access SMB mount point from shell,

As an alternative (and if you like tinkering) you could add something to your /etc/fstab - for example:

//xxx.xxx.xxx.xxx/someshare /home/user/somedir cifs credentials=/root/.smbcredentials,uid=1000,iocharset=utf8,noperm 0 0

1. In the above example; xxx can be either the IP of the server or a name should you have that in your /etc/hosts
2. someshare is the share on the smb server
3. /home/user/somedir would be the dir within your home dir that you can access via terminal or any GUI app (or if you prefer, have the dir in /mnt/somedir)
4. You can include the password of the user in the above line however, I store it in a file (.smbcredential) in the root dir.

This is what I do and mounts the share on login without fail (assuming the server is online and networking is up and functional).
There are many assumptions that should be in place before the above and it sounds like they are so for the sake of time and space, they are not mentioned here.

Last edited by Stratoblaster (2018-12-08 17:49:35)


Supercalifragilisticexpialidocious

Offline

#8 2018-12-09 11:25:29

squalou
Member
Registered: 2018-06-04
Posts: 112

Re: [SOLVED] Access SMB mount point from shell,

Well, I'm not at ease with two things in this approach :
- I change of networks 3 times a day, some resources are available or not depending on the network ... so I doubt in would work in my case. PRice to pay for ultra-mobility kind of jobs I guess.
- storing clear case credentials itches my paranoia ;-)

anyway thanks, I'll probablly adopt this approach on another computer I have in a fix place.

Offline

#9 2018-12-09 17:24:48

Stratoblaster
Member
From: Florida
Registered: 2018-12-04
Posts: 58

Re: [SOLVED] Access SMB mount point from shell,

squalou wrote:

Well, I'm not at ease with two things in this approach :
- I change of networks 3 times a day, some resources are available or not depending on the network ... so I doubt in would work in my case. PRice to pay for ultra-mobility kind of jobs I guess.

Yes - this could be a bit of an issue. I'm not sure if setting nosuid,nodev,nofail  would work in your case (and I should try that in mine to know for certain) I know it works well for my external USB drives. If they are not attached when the system is booted, those bits I mentioned, just tell the system to ignore the errors and move on with the boot process instead of prompting for root access to correct the issue. But to your point, your way may be the easier.

squalou wrote:

- storing clear case credentials itches my paranoia ;-)
anyway thanks, I'll probablly adopt this approach on another computer I have in a fix place.

I agree here too. I need to see if something can be done similar to what I do for mounting my encrypted drives using a key-file as I feel it would bit safer, but still I absolutely understand your point and is valid.

Please keep on mind that as I don't know your setup and requirements, some of the bits above I need to test out for myself as a To-Do.
Just a bit of thinking out loud of possible ways to do things smile

Best
SB

Last edited by Stratoblaster (2018-12-09 17:30:02)


Supercalifragilisticexpialidocious

Offline

Board footer

Powered by FluxBB