Visual studio code Cannot save my files in the openhab folder. Dont have premissions VS says. Help!

Setup, Configuration and Use Beginners
1

Hello.
I am new to all this and have been adding things and item code from putty.
But now i changed and want to use Visual Studio. i have all installed and can reade my files in VS but if i change something i cannot save it. I get the message that i dont have the premissions to save inside openhab.
my openhab is running on RPI3.
Can somone help what can be the reason?

Thanks in advance

2

I am guessing you access your files via samba share now.
So it sounds like a permission issue in your samba config of your openhab files.

3

I have been running through that but i cannot find anything and, i did not change anything in the samba.
is there something you need to change in the samba config?

4

I am not a samba expert either.

Maybe someone else can help.

But it might help if you post your samba config and the output of ls -al /etc/openhab to see the file attributes.

5

[global]

Browsing/Identification

Change this to the workgroup/NT-domain name your Samba server will part of

workgroup = WORKGROUP

Windows Internet Name Serving Support Section:

WINS Support - Tells the NMBD component of Samba to enable its WINS Server

wins support = yes

WINS Server - Tells the NMBD components of Samba to be a WINS Client

Note: Samba can be either a WINS Server, or a WINS Client, but NOT both

; wins server = w.x.y.z

This will prevent nmbd to search for NetBIOS names through DNS.

dns proxy = no

Networking

The specific set of interfaces / networks to bind to

This can be either the interface name or an IP address/netmask;

interface names are normally preferred

; interfaces = 127.0.0.0/8 eth0

Only bind to the named interfaces and/or networks; you must use the

‘interfaces’ option above to use this.

It is recommended that you enable this feature if your Samba machine is

not protected by a firewall or is a firewall itself. However, this

option cannot handle dynamic or non-broadcast interfaces correctly.

; bind interfaces only = yes

Windows Internet Name Serving Support Section:

WINS Support - Tells the NMBD component of Samba to enable its WINS Server

wins support = yes

WINS Server - Tells the NMBD components of Samba to be a WINS Client

Note: Samba can be either a WINS Server, or a WINS Client, but NOT both

; wins server = w.x.y.z

This will prevent nmbd to search for NetBIOS names through DNS.

dns proxy = no

Networking

The specific set of interfaces / networks to bind to

This can be either the interface name or an IP address/netmask;

interface names are normally preferred

; interfaces = 127.0.0.0/8 eth0

Only bind to the named interfaces and/or networks; you must use the

‘interfaces’ option above to use this.

It is recommended that you enable this feature if your Samba machine is

not protected by a firewall or is a firewall itself. However, this

option cannot handle dynamic or non-broadcast interfaces correctly.

; bind interfaces only = yes

Debugging/Accounting

This tells Samba to use a separate log file for each machine

that connects

log file = /var/log/samba/log.%m

Cap the size of the individual log files (in KiB).

max log size = 1000

If you want Samba to only log through syslog then set the following

parameter to ‘yes’.

syslog only = no

We want Samba to log a minimum amount of information to syslog. Everything

should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log

through syslog you should set the following parameter to something higher.

syslog = 0

Do something sensible when Samba crashes: mail the admin a backtrace

; panic action = /usr/share/samba/panic-action %d

####### Authentication #######

Server role. Defines in which mode Samba will operate. Possible

values are “standalone server”, “member server”, "classic primary

domain controller", “classic backup domain controller”, "active

directory domain controller".

Most people will want “standalone sever” or “member server”.

Running as “active directory domain controller” will require first

new domain.

server role = standalone server

If you are using encrypted passwords, Samba will need to know what

password database type you are using.

passdb backend = tdbsam
obey pam restrictions = yes

This boolean parameter controls whether Samba attempts to sync the Unix

password with the SMB password when the encrypted SMB password in the

passdb is changed.

unix password sync = yes

For Unix password sync to work on a Debian GNU/Linux system, the following

parameters must be set (thanks to Ian Kahan <kahan@informatik.tu-muenchen.de for

sending the correct chat script for the passwd program in Debian Sarge).

passwd program = /usr/bin/passwd %u
passwd chat = Enter\snew\s\spassword:* %n\n Retype\snew\s\spassword:* %n\n password\supdated\ssuccessfully .

This boolean controls whether PAM will be used for password changes

when requested by an SMB client instead of the program listed in

‘passwd program’. The default is ‘no’.

pam password change = yes

This option controls how unsuccessful authentication attempts are mapped

to anonymous connections

map to guest = bad user

########## Domains ###########

The following settings only takes effect if 'server role = primary

classic domain controller’, ‘server role = backup domain controller’

or ‘domain logons’ is set

It specifies the location of the user’s

profile directory from the client point of view) The following

required a [profiles] share to be setup on the samba server (see

below)

; logon path = \%N\profiles%U

Another common choice is storing the profile in the user’s home directory

(this is Samba’s default)

logon path = \%N%U\profile

The following setting only takes effect if ‘domain logons’ is set

It specifies the location of a user’s home directory (from the client

point of view)

; logon drive = H:

logon home = \%N%U

The following setting only takes effect if ‘domain logons’ is set

It specifies the script to run during logon. The script must be stored

in the [netlogon] share

NOTE: Must be store in ‘DOS’ file format convention

; logon script = logon.cmd

This allows Unix users to be created on the domain controller via the SAMR

RPC pipe. The example command creates a user account with a disabled Unix

password; please adapt to your needs

; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos “” %u

This allows machine accounts to be created on the domain controller via the

SAMR RPC pipe.

The following assumes a “machines” group exists on the system

; add machine script = /usr/sbin/useradd -g machines -c “%u machine account” -d /var/lib/samba -s /bin/false %u

This allows Unix groups to be created on the domain controller via the SAMR

RPC pipe.

; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

Using the following line enables you to customise your configuration

on a per machine basis. The %m gets replaced with the netbios name

of the machine that is connecting

; include = /home/samba/etc/smb.conf.%m

Some defaults for winbind (make sure you’re not using the ranges

for something else.)

; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash

Setup usershare options to enable non-root users to share folders

with the net usershare command.

Maximum number of usershare. 0 (default) means that usershare is disabled.

; usershare max shares = 100

Allow users who’ve been granted usershare privileges to create

public shares, not just authenticated ones

; usershare allow guests = yes

#======================= Share Definitions =======================

[homes]
comment = Home Directories
browseable = no
valid users = %S
writeable = yes
create mask = 0700
directory mask = 0700

[printers]
comment = All Printers
browseable = no
public = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700

Windows clients look for this share name as a source of downloadable

printer drivers

[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = no
public = no
read only = yes
guest ok = no

Uncomment to allow remote administration of Windows print drivers.

You may need to replace ‘lpadmin’ with the name of the group your

admin users are members of.

Please note that you also need to set appropriate Unix permissions

to the drivers directory for these users to have write rights in it

; write list = root, @lpadmin

#=================== Custom Share Definitions ====================

[openHAB-share]
comment=openHAB2 combined folders
path=/srv
writeable=yes
public=no
create mask=0664
directory mask=0775
veto files = /Thumbs.db/.DS_Store/..DS_Store/.apdisk/.*/
delete veto files = yes

[openHAB-conf]
comment=openHAB2 site configuration
path=/etc/openhab2
writeable=yes
public=no
create mask=0664
directory mask=0775

6

But is there any changes you need to do in the Samba conf to get access ?

7

Do you have openhabian config installed?

If so run the fox permissions item. Do nt remember what tab it is under.

1 Like
8

@Thedannymullen good idea using the openhabian tools :+1:

sudo openhabian-config

I didn’t see a fox permissions,:wink: but you can find fix permissions (#14) under “Apply Improvements”

2 Likes
9

As per the installation docs, I have:

create mask=0777
directory mask=0777

In each of the shares

10

If you mean openhab in VS code then yes.

11

Can any of you guys share you samba settings?

12

Set your config to look like this, changing only the openhab-share and openhab-conf part, and give it a try.

Screenshot%20at%202018-09-20%2008-58-15

13

This is still not working. more help please :slightly_smiling_face:

14

What @Thedannymullen was saying, is from the terminal type this:

sudo openhabian-config

You will then be able to arrow down and select “Apply Improvements” then select #14 “Fix Permissions”

This tool will help with all openhab2 permissions.

1 Like