[Samba] PDC migration: printing trouble. Summary.

[Ryan Novosielski]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Remy Zandwijk wrote:

> Second: all printers had an 'invalid users' setting in the share
> definition.
> It turned out that this considerably stresses the CPU. It took about 10
> seconds for the properties to show up for a 'HP 4250PS driver' printer.
> While
> truss-ing the smbd process, we saw that the smbpasswd file was opened
> for 85
> times (from the click on 'properties' to when the properties appeared). I
> think that's a lot. We have around 4700 entries in the smbpasswd file, so I
> can imagine why it takes long for the properties to show up when 6 invalid
> users are configured. Only one would expect that the smbpasswd file is
> opened
> just 6 to 10 times, and not 85 times. I guess this won't happen when
> using a
> tdbsam passdb backend (which is not an option for us for now).

I can confirm that your results will be much improved in all respects
when you move to a proper backend. In our situation, the PW file was
always locked as a result of too many reads and we were entirely unable
to change passwords for a period of time. In fact, I would encourage you
to do something about this before you get bitten by it, because with the
file being read so often, you may run into this problem too.

- --
 ---- _  _ _  _ ___  _  _  _
 |Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Systems Programmer II
 |$&| |__| |  | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922)
 \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIH/qDmb+gadEcsb4RAunyAJ4lasxw461nCH54dxOlW+/Tm+QjQgCeIwXE
YQg/Zb8tE//I537bvacM6RY=
=AvXg
-----END PGP SIGNATURE-----