samba - Sep 2021 - Possible memory leak in

All I do is add these lines to smb.comf under global.:
client min protocol = NT1
server min protocol = NT1
usershare owner only = false
force user = moursbourn

I do not know what the NT1 stuff does other than it helped windows see the
share.

*Here is the output:*

Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Weak crypto is allowed

Server role: ROLE_STANDALONE

# Global parameters
[global]
        client min protocol = NT1
        log file = /var/log/samba/log.%m
        logging = file
        map to guest = Bad User
        max log size = 1000
        obey pam restrictions = Yes
        pam password change = Yes
        panic action = /usr/share/samba/panic-action %d
        passwd chat = *Enter\snew\s*\spassword:* %n\n
*Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
        passwd program = /usr/bin/passwd %u
        server min protocol = NT1
        server role = standalone server
        unix password sync = Yes
        usershare allow guests = Yes
        usershare owner only = No
        idmap config * : backend = tdb
        force user = moursbourn


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


[printers]
        browseable = No
        comment = All Printers
        create mask = 0700
        path = /var/spool/samba
        printable = Yes


[print$]
        comment = Printer Drivers
        path = /var/lib/samba/printers


----
-matt

On Sat, Sep 11, 2021 at 11:55 AM Rowland Penny via samba <
samba at lists.samba.org> wrote:
> On Sat, 2021-09-11 at 11:33 -0700, Matt Oursbourn wrote:
> > I might have spoken too soon.  Just to give it more headroom I added
> > another 32GB of ram to the machine.   Now it has 64GB.   As of this
> > morning Samba is using 32.6GiB.   Is samba supposed to use this much
> > ram or is something else going on?   At least so far it has not
> > crashed with the 64GB of ram.
> >
>
> No one else has reported high ram usage (this doesn't mean it isn't
> occurring elsewhere). Just on the off chance that you are doing
> something strange, can we see your smb.conf, this will also show us how
> you are running Samba.
>
> Rowland
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>

On Sat, 2021-09-11 at 12:50 -0700, Matt Oursbourn wrote:
> All I do is add these lines to smb.comf under global.:  
> client min protocol = NT1
> server min protocol = NT1
> usershare owner only = false
> force user = moursbourn
> 
> I do not know what the NT1 stuff does other than it helped windows
> see the share.
It allows the use of SMBv1, which is required for network browsing.
> 
> Here is the output:
> 
> Load smb config files from /etc/samba/smb.conf
> Loaded services file OK.
> Weak crypto is allowed
> 
> Server role: ROLE_STANDALONE
> 
> # Global parameters
> [global]
>         client min protocol = NT1
>         log file = /var/log/samba/log.%m
>         logging = file
>         map to guest = Bad User
>         max log size = 1000
>         obey pam restrictions = Yes
>         pam password change = Yes
>         panic action = /usr/share/samba/panic-action %d
>         passwd chat = *Enter\snew\s*\spassword:* %n\n
> *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
>         passwd program = /usr/bin/passwd %u
>         server min protocol = NT1
>         server role = standalone server
>         unix password sync = Yes
>         usershare allow guests = Yes
>         usershare owner only = No
>         idmap config * : backend = tdb
>         force user = moursbourn
Just about the only problem (and it is probably only a slight problem)
is the use of 'force user', it is really only meant to be in a share
and I cannot understand why you added it.

You also do not seem to have any shares apart from the 'homes' share,
what are you copying the data to/from ?

Rowland