Topic: Samba includes - smb.conf.%m

[bloodshoteye]

Hi all
I've looked thru the forum but not found a solution.
I'm wanting to apply the following include in Samba:

include = /etc/smb.conf/ehsSamba/smb.conf.%m

I have created a snippet in /etc/e-smith/templates-custom/etc/smb.conf/11include:

{
# 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 = /etc/smb.conf/ehsSamba/smb.conf.%m

Path to machine conf:

/etc/e-smith/templates-custom/etc/smb.conf/ehsSamba/smb.conf.tinprint
I placed a modified conf file in there called smb.conf.tinprint

Then expanded the template & restarted smb service. The machine conf is not applied.
I'm using a fully patched 7.3 installation.
Any ideas on what I'm doing wrong, please?

Thanks,
 

[Boris]

include = /etc/smb.conf/ehsSamba/smb.conf.%m

Is smb.conf in your case folder or file?

[bloodshoteye]

Hi, boris

Is smb.conf in your case folder or file?

Sorry, but I'm not sure what you mean - can you provide a little more background, please?

[Boris]

/etc/e-smith/templates-custom/etc/smb.conf/11include

This line above suggested, that you trying to add 11include fragment to /etc/smb.conf file.
BTW for sme 7.3 it should be located in /etc/samba/ folder and template should be placed in /etc/e-smith/templates-custom/etc/samba/smb.conf/11include

Apart from path to smb.conf is wrong for SME 7.3 again, the line below referes to smb.conf as a folder, since the full path is shown /set/smb.conf/ehsSamba/
include = /etc/smb.conf/ehsSamba/smb.conf.%m

Its not clear of what you are trying to do.

[bloodshoteye]

Boris,
I cannot carry out your suggestion until I recover from an operation, so if I may take a raincheck for a couple of weeks?

Thanks,

[pfloor]

/etc/e-smith/templates-custom/etc/smb.conf/11include

This line above suggested, that you trying to add 11include fragment to /etc/smb.conf file.
BTW for sme 7.3 it should be located in /etc/samba/ folder and template should be placed in /etc/e-smith/templates-custom/etc/samba/smb.conf/11include

Boris, that is not correct.  The correct paths for /etc/samba/smb.conf templates are:

/etc/e-smith/templates/etc/smb.conf/ <for regular templates
/etc/e-smith/templates-custom/etc/smb.conf/ <for custom templates

See bug http://bugs.contribs.org/show_bug.cgi?id=87

AFAIK, this is the only template directory that is this way and if memory serves me correctly, it is for some backwards compatibility/upgrade issues from older versions because smb.conf was moved and the templates were not.

[bloodshoteye]

pfloor

please take a look at my original question - is it ok create an arbitrary subdir for an include as I did:

include = /etc/smb.conf/ehsSamba/smb.conf.%m

After all it is a subdir of smb.conf.

[pfloor]

pfloor

please take a look at my original question - is it ok create an arbitrary subdir for an include as I did:After all it is a subdir of smb.conf.

Here lies your confusion, /etc/smb.conf doesn't exist and /etc/samba/smb.conf isn't a directory, it is a file.  Also, a subdirectory within templated file doesn't create another directory.  Let me see if I can help you with this.

If you haven't already done so, create a DIRECTORY called  /etc/e-smith/templates-custom/etc/smb.conf

In that directory, create a custom template called 11include2 <--Note the "2" at the end.  This causes this new template to be generated just after the existing 11include template and add your changes in the correct order in smb.conf.

In that template ADD your include directive but CHANGE it to:

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

If you haven't already done so, now create another DIRECTORY called  /etc/e-smith/templates-custom/etc/samba/smb.conf.tinprint

Then create your template (or template fragments) for smb.conf.tinprint and place them there.

These 2 steps should create the "include" line in /etc/samba/smb.conf and another file called /etc/samba/smb.conf.tinprint.  I *think* this is what you are after.

I suggest you read http://mirror.contribs.org/smeserver/contribs/gordonr/devguide/html/devguide.html#TEMPLATES as it will give you more insight on how the templates work.

[CharlieBrady]

If you haven't already done so, create a DIRECTORY called  /etc/e-smith/templates-custom/smb.conf

I believe that you mean /etc/e-smith/templates-custom/etc/samba/smb.conf

In that template ADD your include directive but CHANGE it to:

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

That looks good.

If you haven't already done so, now create another DIRECTORY called  /etc/e-smith/templates-custom/samba/smb.conf.tinprint

Here you mean:

/etc/e-smith/templates-custom/etc/samba/smb.conf.tinprint

But if the desired include path really is:

/etc/smb.conf/ehsSamba/smb.conf.%m

then that could be used as well - the template directory would be /etc/e-smith/templates-custom/etc/smb.conf/ehsSamba/smb.conf.tinprint

These 2 steps should create the "include" line in /etc/samba/smb.conf and another file called /etc/samba/smb.conf.tinprint.

/etc/samba/smb.conf.tinprint will only be created after ardugh runs:

expand-template /etc/samba/smb.conf.tinprint

Alternatively, ardugh could just create /etc/samba/smb.conf.tinprint without templating it. The only problem with this is that file won't be included in a backup/restore.

[pfloor]

I believe that you mean /etc/e-smith/templates-custom/etc/samba/smb.conf

Sorry, a typo but I did mean /etc/e-smith/templates-custom/etc/smb.conf (fixed above) but as I read the metadata files it looks like either path will work.  Thus lies the confusion about smb.conf.

The file lies here: /etc/samba/smb.conf
The template directory is here: /etc/e-smith/templates/etc/smb.conf
And custom templates should go here?: /etc/e-smith/templates-custom/etc/samba/smb.conf
I've always put smb custom templates here:  /etc/e-smith/templates-custom/etc/smb.conf

So as I understand it, either location will work.

Here you mean:

/etc/e-smith/templates-custom/etc/samba/smb.conf.tinprint

Yes, that is correct (typo AGAIN, I will edit it).

But if the desired include path really is:

/etc/smb.conf/ehsSamba/smb.conf.%m

then that could be used as well - the template directory would be /etc/e-smith/templates-custom/etc/smb.conf/ehsSamba/smb.conf.tinprint

You could do that but it adds an additional directory where samba related files would be kept (/etc/smb.conf/...).  I think the location of the templates vs the location of smb.conf is what threw ardugh off, and thus all the different approaches shown here.

ardugh, where exactly do you want smb.conf.tinprint?

Your original post has it here /etc/smb.conf/ehsSamba/smb.conf.tinprint but /etc/smb.conf/ does not exist so you would be adding an additional location for samba related config files.

/etc/samba/ehsSamba/smb.conf.tinprint would be better but adds an additional subdirectory.

My initial instructions put it with the rest of the samba config files at /etc/samba/

Where do you want it to be?

[bloodshoteye]

pfloor

I think the location of the templates vs the location of smb.conf is what threw ardugh off, and thus all the different approaches shown here.

You're correct - I'm hoping this will be resolved in v8, but if not perhaps a detailed howto would be nice.

where exactly do you want smb.conf.tinprint?

Anywhere, I guess, but on reflection in the same area as other custom smb templates would be best - Charlie Brady's comment re backups is relevant here.
Because I will need quite a few machine templates, a dedicated sub directory would be best, which is why I thought of:
/etc/e-smith/templates-custom/etc/smb.conf/ehsSamba/smb.conf.%m
- the directory ehsSamba would thus contain all the machine confs.

According to you & Charlie Brady, my mistake is an incorrect original include fragment path, which should be:

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

But would that find the "ehsSamba" machine confs?

[pfloor]

pfloorYou're correct - I'm hoping this will be resolved in v8, but if not perhaps a detailed howto would be nice.

I don't think it will change.  The location of smb.conf was moved from /etc/ to /etc/samba/ and the current template system takes that into account for backward compatibility reasons.

Anywhere, I guess, but on reflection in the same area as other custom smb templates would be best - Charlie Brady's comment re backups is relevant here.
Because I will need quite a few machine templates, a dedicated sub directory would be best, which is why I thought of:
/etc/e-smith/templates-custom/etc/smb.conf/ehsSamba/smb.conf.%m
- the directory ehsSamba would thus contain all the machine confs.

In that case, you need the following:

-create a directory called  /etc/e-smith/templates-custom/etc/smb.conf
-copy the 11include template fragment to the new directory and change it as follows:

Code: [Select]

{
# 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 = /etc/samba/ehsSamba/smb.conf.%m
-Create a directory called /etc/samba/ehsSamba/
-Create a custom template directory called /etc/e-smith/templates-custom/etc/samba/ehsSamba/smb.conf.tinprint/
-In that directory put your template (or template fragments).

expand-template /etc/smb.conf
expand-template /etc/samba/ehsSamba/smb.conf.tinprint

Or if you have many machines you can use:
expand-template /etc/samba/ehsSamba/*
And it will expand all the conf files under ehsSamba all at once.

Now your machine conf files is under /etc/samba/ehsSamba/ and if you add more machines they can go there as well by adding additional custom template directories like:
/etc/e-smith/templates-custom/etc/samba/ehsSamba/smb.conf.machineX/ and placing the template (or template fragments) for that machine there.

Now everything will get backed up and easily restored/upgraded.

Hope that helps.

-Paul

[bloodshoteye]

Paul, I conclude:

Now your machine conf files is under /etc/samba/ehsSamba/ and if you add more machines they can go there as well by adding additional custom template directories like:
/etc/e-smith/templates-custom/etc/samba/ehsSamba/smb.conf.machineX/ and placing the template (or template fragments) for that machine there.

If I understand you correctly, in this particular case I need a hierarchy of directories. To have a semblance of order, I have "ehsSamba" collectively holding individual directories named after machines and in each of these "machine directories" there must be a "11include" conf file particular to that machine.

I doubt I would have figured this out by myself.
Thanks for all the input from those who have helped. I will put this into practice as soon as my convalescence period is over and report back to the list.

[bloodshoteye]

Hi all,

Ok, I tried this (even rebooted once):
1) put the following into /etc/e-smith/templates-custom/etc/smb.conf/11include

include = /etc/smb.conf/ehsSamba/smb.conf.%m

2) Created a directory called /etc/samba/ehsSamba/
(this is where expand-template will place custom confs.)

3) Created a custom template directory called /etc/e-smith/templates-custom/etc/samba/ehsSamba/smb.conf.tinprint/smb.conf
(this is where I placed customized machine confs.)

3) expand-template /etc/smb.conf

4) expand-template /etc/samba/ehsSamba/*
Fails with following error:

# expand-template /etc/samba/ehsSamba/*
ERROR: No templates were found for /etc/samba/ehsSamba/*.
 at /sbin/e-smith/expand-template line 45

(I also tried specifically naming a conf file as in: expand-template /etc/samba/ehsSamba/smb.conf.tinprint
and got the same result.

I tried a previous suggestion and created:
/etc/e-smith/templates-custom/etc/smb.conf/ehsSamba/smb.conf.tinprint/smb.conf
I get the same error when running expand-template as above.

Any ideas, pfloor and CharlieBrady, if you will?

[pfloor]

2) Created a directory called /etc/samba/ehsSamba/

That looks OK

3) Created a custom template directory called /etc/e-smith/templates-custom/etc/samba/ehsSamba/smb.conf.tinprint/smb.conf
(this is where I placed customized machine confs.)

It looks like you have an extra directory (/smb.conf).  You need a template (or template fragments) under /smb.conf.tinprint/ not another directory.  The template fragments will then create the file located at /etc/samba/ehsSamba/ and that file will be called smb.conf.tinprint.

The way you have it now it will create a file located at /etc/samba/ehsSamba/smb.conf.tinprint/ and the file will be called smb.conf

Does that make sense?

[bloodshoteye]

pfloor,

It looks like you have an extra directory (/smb.conf).

Actually the smb.conf referred to here: /etc/e-smith/templates-custom/etc/samba/ehsSamba/smb.conf.tinprint/smb.conf
is a file. The file contains the edited smb.conf for thar particular machine, tinprint.
Should I call the file something other than smb.conf?

[pfloor]

I must apologize, I missed one "small" step.  You must create an empty file of the one you are trying to create through the template system.  IOW:

touch /etc/samba/ehsSamba/smb.conf.tinprint

pfloor,
Actually the smb.conf referred to here: /etc/e-smith/templates-custom/etc/samba/ehsSamba/smb.conf.tinprint/smb.conf
is a file. The file contains the edited smb.conf for thar particular machine, tinprint.
Should I call the file something other than smb.conf?

It doesn't matter but you may want to call it something else to eliminate confusion and really utilize the power of the template system.  Template fragments are generally called 10something, 20something, etc and expanded in order.  If you had 10something and 20something-else and wanted to add something in the middle then you would create 15additional-something.

So with that said, I would do it like this and here are ALL the steps all written out in CL:

(NOTE: I have changed the name of your custom template fragment to 10MachineConf).

Create your custom template directory smb.conf and copy 11include:

Code: [Select]

mkdir -p /etc/e-smith/templates-custom/etc/smb.conf
cp /etc/e-smith/templates/etc/smb.conf/11include /etc/e-smith/templates-custom/etc/smb.conf

Now edit /etc/e-smith/templates-custom/etc/smb.conf/11include to suite your needs.

Create your machine's conf directory and (empty) file.

Code: [Select]

mkdir -p /etc/samba/ehsSamba
touch /etc/samba/ehsSamba/smb.conf.tinprintNote the new "touch" command that I missed in my initial instructions.

Now create the custom template directory and (empty) template fragment.

Code: [Select]

mkdir -p /etc/e-smith/templates-custom/etc/samba/ehsSamba/smb.conf.tinprint
touch /etc/e-smith/templates-custom/etc/samba/ehsSamba/smb.conf.tinprint/10MachineConf
Now edit /etc/e-smith/templates-custom/etc/samba/ehsSamba/smb.conf.tinprint/10MachineConf to suite your needs.

Code: [Select]

expand-template /etc/smb.conf
expand-template /etc/samba/ehsSamba/smb.conf.tinprint
Or if you have multiple machine conf files:

Code: [Select]

expand-template /etc/samba/ehsSamba/*
And then of course you must restart samba for your changes to take effect.

Next lesson: How to utilize the config db with templates so your config files are generated via db settings...Oh wait, that will take way too much time

If you have a test test machine (VMWare is great for this) you should read the developer's manual and play around.  Here is the section on templates: http://wiki.contribs.org/SME_Server:Documentation:Developers_Manual#Configuration_file_templates but I would suggest you start from the beginning.  You will probably need to read it at least 3 times before you begin to get your head around it.  I have read all of it 5 times and still don't understand 50% of it

[CharlieBrady]

If you haven't already done so, now create another DIRECTORY called  /etc/e-smith/templates-custom/etc/samba/smb.conf.tinprint

Then create your template (or template fragments) for smb.conf.tinprint and place them there.

These 2 steps should create the "include" line in /etc/samba/smb.conf and another file called /etc/samba/smb.conf.tinprint.  I *think* this is what you are after.

Paul, I think you are trying to make this more complicated than it needs to be. I don't see anything here which sugggests that the individual fragments to be included need to be templated. As long as smb.conf contains the "include ....%m" line which has been requested, then smb.conf.tinprint and smb.conf.* for other workstations can each be individually created containing whatever is wanted.

We don't appear to have been told what problem is trying to be solved, or what the content of the individual smb.conf.%m files will be, so it's hard to help further.

[bloodshoteye]

pfloor,

Thanks, I will carry out your suggestion later this afternoon when the network is quieter. Thanks for spending time on this - I appreciate it.

######
EDITS - moved (by me) to a reply to this thread.
######

CharlieBrady,

Perhaps my original post was not clear enough. I need to apply samba machine configurations to pupils who are logging on to an exam session, in our case, starting tomorrow June 3... They will have adjusted environments during the session, and I've always used samba machine confs in the past. Seating is random during exams, thus the need for  machine confs. These must be removed after the session/s, obviously.

[bloodshoteye]

Hi

Reporting back on progress to date:

A test shows the empty file in /etc/samba/ehsSamba/smb.conf.tinprint now contains the contents of /etc/e-smith/templates-custom/etc/samba/ehsSamba/smb.conf.tinprint/10MachineConf - just as you have detailed.

1) Early testing shows the need to comment out lines in the Login Scrip Manager contrib, which is used to map a number of drives using the #ifg groupname1, groupname2 syntax. These are not offered via the edited machine conf, but are still available to exam candidates unless commented out.

2) For some reason I have to do - 67 times  :
expand-template /etc/smb.conf
expand-template /etc/samba/ehsSamba/smb.conf.<machine_name>
for each custom template - appending a star doesn't do anything??

[CharlieBrady]

2) For some reason I have to do - 67 times  :
expand-template /etc/smb.conf
expand-template /etc/samba/ehsSamba/smb.conf.<machine_name>
for each custom template

You wouldn't need to do that if you didn't template the 67 individual config files, but just edited each directly, as required.

- appending a star doesn't do anything??

No, expand-template only expands a single file. Using * creates a list of files, and only the first one is processed.

[bloodshoteye]

CharlieBrady

You wouldn't need to do that if you didn't template the 67 individual config files, but just edited each directly, as required.

My previous post was a bit misleading - i didn't have to do expand-template /etc/smb.conf multiple times, just expand-template /etc/samba/ehsSamba/smb.conf.<machine_name>
As you said, expand-template only expands a single file.

You wouldn't need to do that if you didn't template the 67 individual config files, but just edited each directly, as required

I don't quite get this - where would I edit each directly as required?

[CharlieBrady]

I don't quite get this - where would I edit each directly as required?

You would edit each /etc/samba/ehsSamba/smb.conf.<machine_name>. If you are not configuring any configuration or accounts database information in those files, then they don't need to be templated.

[bloodshoteye]

You would edit each /etc/samba/ehsSamba/smb.conf.<machine_name>. If you are not configuring any configuration or accounts database information in those files, then they don't need to be templated.

The idea is to provide them with access only to ~home/
All other samba shares must be denied (to them, while staff must work as usual). I know the machine names they will use. I move existing homes to a holding area and replace them with a specially prepared ~/home containing exam questions. They get new profile directories too, in case enterprising pupils have hidden work somewhere in the myriads of directories m$ provides in profiles.

They all get a standard cut-down machine fragment, which I'm not sure worked today. I also remmed out drive mappings in the Login Script Manager contrib. Their "My Computer" only showed the so called "exam" home drive, but one or two found they could still map a drive to samba shares they have rights to.
I then used standard Linux permissions and denied Group & Others access to these shares - that kept them out.

In the end, the whole process seems needlessly complicated.
I strongly wish these particular teachers would investigate moodle.
But that won't help in grade 12 - their final is very strictly controlled and moodle will not be an option, as far as I can see.