Triode,
Just catching up with your addition of a "SAMBA" server to
soa-aur/soa-web a couple of days ago. I think you intended anything
under /mnt to be visible via the soa-aur SAMBA server and to be
read/write. But there's a permission problem when I tested this. For
example, first add a NFS vers=3 mount, and then activate the SAMBA
server to share it across all devices on the same network.
Code:
--------------------
[root@alarm ~]# cat /etc/fstab
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
# start added by soa-web
192.168.0.20:/media/allmusic/Test /mnt/disk1 nfs vers=3 0
0
# end added by soa-web
--------------------
Code:
--------------------
Jul 29 15:32:04 alarm nmbd[268]:
Jul 29 15:32:04 alarm nmbd[268]: Samba name server "SOA" is now a local
master browser for workgroup "WORKGROUPQM" on subnet 192.168.0.111
Jul 29 15:32:04 alarm nmbd[268]:
Jul 29 15:32:04 alarm nmbd[268]: *****
Jul 29 15:41:48 alarm smbd[316]: [2014/07/29 15:41:48.947891, 0]
../source3/printing/print_cups.c:151(cups_connect)
Jul 29 15:41:48 alarm smbd[316]: Unable to connect to CUPS server
/var/run/cups/cups.sock:631 - Bad file descriptor
Jul 29 15:41:48 alarm smbd[284]: [2014/07/29 15:41:48.962356, 0]
../source3/printing/print_cups.c:528(cups_async_callback)
Jul 29 15:41:48 alarm smbd[284]: failed to retrieve printer list:
NT_STATUS_UNSUCCESSFUL
Jul 29 15:43:45 alarm systemd[1]: Starting Cleanup of Temporary Directories...
Jul 29 15:43:47 alarm systemd[1]: Started Cleanup of Temporary Directories.
--------------------
The smb conf file maps all access to guest user "nobody", but the owner
of "/mnt/disk1" is something different and of course /mnt has root as
owner/group.
In may case I have :
Code:
--------------------
[root@alarm mnt]# ls -l
total 24
drwxr-xr-x 4 1000 1000 4096 Jul 29 16:26 disk1
drwxr-xr-x 2 root root 4096 Jul 13 17:14 disk2
drwxr-xr-x 2 root root 4096 Jul 13 17:14 disk3
drwxr-xr-x 2 root root 4096 Jul 13 17:14 disk4
drwxr-xr-x 2 root root 4096 Jul 13 17:14 disk5
drwxr-xr-x 2 root root 4096 Jul 13 17:14 disk6
--------------------
Hence, the share is visible, but you get permission errors when trying
to write to the SAMBA server file share as the user nobody has uid of 99
on the system and not 1000. The original CSOS project had a separate
mount point for the Wandboard internal SAMBA server:
Code:
--------------------
drwxrwxrwx. 7 nobody nobody 4096 Apr 2 12:25 storage
--------------------
Also, you get nagging messages re: cups and printer lists when
activating the SAMBA server using the current /etc/samba/soa-smb.conf
which is copied to /etc/samba/smb.conf (see part of journalctl output
above). You can avoid this by adding these lines to the smb.conf global
section:
Code:
--------------------
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = yes
--------------------
------------------------------------------------------------------------
Krisbee's Profile: http://forums.slimdevices.com/member.php?userid=59080
View this thread: http://forums.slimdevices.com/showthread.php?t=101624
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
