Custom SMB config troubleshooting

[Marko Polo]

I've added some config option to smb.conf following the wiki, and it was added, but it was added in the end of smb.conf, i.e. to one of the shares. It commonly known, the structure of smb.conf is

[global options]
[share 1 options]
[share 2 options]
[share n options]

How to add my option to the global section? Should I specify section just in smb.conf.add? In the examples of .add file I met here, I found only pure lines, no section specification.

Thx.

 

[ColinTaylor]

You can only do it with a postconf script. Use the pc_insert command to match an existing string (like "[global]") and it will insert something on the following line:

#!/bin/sh

CONFIG=$1
source /usr/sbin/helper.sh

pc_insert "[global]" "min protocol = NT1" $CONFIG

https://github.com/RMerl/asuswrt-merlin/wiki/Custom-config-files#postconf-scripts

 

[Marko Polo]

You can only do it with a postconf script. Use the pc_insert command to match an exsiting string (like "[global]") and it will insert something on the following line:

Doesn't work for some reason. Maybe one should backslash the brackets?

 

[ColinTaylor]

Doesn't work for some reason. Maybe one should backslash the brackets?

Just tried it here and it works without any changes.

admin@RT-AC68U:/tmp/home/root# cat /etc/smb.conf
[global]
min protocol = NT1
workgroup = HOME
netbios name = RT-AC68U
server string = RT-AC68U
:
:
:

You have given the script the correct name? smb.postconf

 

[Marko Polo]

Figured it out. Yes, the name was correct, however permissions were not 0777, like in other scripts. After I fixed this, all started to work.
But there is no single word in the wiki about permissions thing.

 

[ColinTaylor]

But there is no single word in the wiki about permissions thing.

Well it is described in here, and if the person writing it was a "Unix guy" they probably subconsciously assumed people knew this (because it's a script).

 

[Marko Polo]

Well it is described in here

Well, will read the wiki in a cross-paging manner And chmod a+rx sets 0775 perms. So 0775 is sufficient and no need for 0777?

 

[thelonelycoder]

And chmod a+rx sets 0775 perms.

chmod a+rx sets them to 0755, which is sufficient rights to run them.

 

[ColinTaylor]

chmod a+rx sets them to 0755, which is sufficient rights to run them.

Strictly speaking a+rw adds 0555 to the permissions that already exist.

As the owner of the file almost certainly already has write access , this leads to at least 0755 but possibly higher.

As there is no assumption that the owner of the file is the same as the user account that will be executing it, rx permissions need to be set for all users.

Out of habit I tend to just use "chmod 755 myfile" which removes write permissions for non-owners if they have already been set.

Just being pedantic.

 

[thelonelycoder]

Strictly speaking a+rw adds 0555 to the permissions that already exist.

As the owner of the file almost certainly already has write access , this leads to at least 0755 but possibly higher.

As there is no assumption that the owner of the file is the same as the user account that will be executing it, rx permissions need to be set for all users.

Out of habit I tend to just use "chmod 755 myfile" which removes write permissions for non-owners if they have already been set.

Just being pedantic.

It's a good habit, AB-Solution uses 0755 or less where needed.