System: samba 2.0.4b on Solaris 2.x
Starting point: PC's "Properties" window on a share of home
directories;
diskspace Used/Free "pie-chart" and figures.
A colleague asked me yesterday whether this properties window could
display the diskspace information, using the user's UNIX quota rather than
the physical space on the disk.
Our environment has potentially 14,000 users, each with a home directory
on samba. On a typical UNIX volume there are several hundred users, with
their occupancy and free-space controlled by quota (contrast with a single
user, whose occupancy and free-space would be governed by the physical
capacity of the volume). In this environment it would be far more natural
for all these "Properties" figures and the pie chart to show occupancy
and
free-space from the quota, rather than from "df"-type output.
Naturally I did a quick "grep -i quota" through the samba
distribution.
Though this indicated an experimental "--with-quotas" option, there is
apparently no documentation. Having re-built samba using
"--with-quotas",
the "Properties" still shows physical diskspace.
(a) What does the "with-quotas" try to do?
(b) Where is it documented?
(c) How, if at all, does it relate to the "Properties" information on
a
share?
(d) Does my idea above seem reasonable? (If not, then why not, please?)
(e) Assuming it is reasonable, should I have a go at trying to implement
it, presumably using a new "smb.conf(5)" option to enable it?
--
: David Lee I.T. Service :
: Systems Programmer Computer Centre :
: University of Durham :
: Phone: +44 191 374 2882 (ddi) South Road :
: Fax: +44 191 374 7759 Durham :
: Internet: T.D.Lee@durham.ac.uk U.K. :
Samba Heros: I am having trouble building the guest options into the latest samba. I am building samba 2.0.3 on a Solaris 2.6 system. The docs state that the guest access can be compiled into the binary by setting a parameter in a specific header file. First, does anyone know what variable this is? In which header file? Basically I want to compile REAL guest access into samba, so I do not have to open UNIX permissions up to wide in order to make a share available without a password prompt. In addition I want guest access to work the same way for local printing. So what should I set this to. If I remember correctly the variable had to be set to 0,1,or 2. Thanks in advance for you help. Jamey
James Strauch wrote:> > way for local printing. So what should I set this to. If I remember > correctly the variable had to be set to 0,1,or 2.In 2.0.x, this is a now a smb.conf parameter. See the man page on map to guest Cheers, jery ________________________________________________________________________ Gerald ( Jerry ) Carter Engineering Network Services Auburn University jerry@eng.auburn.edu http://www.eng.auburn.edu/users/cartegw "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 )
>You wrote: >| Actually I wrote a hack for this functionality myself about a year back; >| it was simply a matter of rewriting the unlink() routine, so that not >| only would it keep a copy of a file before being deleted, but also >| keep several revisions of the file. > > In a previous life, I implemented a version of the > VMS-like versioned files by changing open on a non-u > system.[...]> I like changing unlink better, so that one could > subsequently say 'rm foo;1' and have it really disappear.Actually, it was a combination of a rewritten [f][re]open() and unlink() - a different unlink() allone would not keep older versions of files being changed rather than deleted. It then re#define'd all calls to [f][re]open()/unlink() in the samba code to my own routines. I've also seen someone talking about changing this in the kernel or libc. I believe that is where it should be - perhaps as an extention of the filesystem. Unfortunately that doesn't help people running samba on a non-open kernelcode box =(> There is another person at the samba-list seems done the similar > work as u do. maybe u can contact him....I'm not a samba developer but am willing to re-implement this - at least efforts should be co-ordinated. With whoem and how is this done?> ps: my little suggestion: if we add some parameters at smb.conf like > protected dir = /home/share, /home/user1 ; > trashcan dir = /smbtrash ;My hack simply applied to all shares that samba offered. Putting a filter descision here makes me be concerned about performance... there is a *lot* of file I/O =/ It also completely replicated the original (native filesystem) path relative to the "trashcan" directory; a win95/98-like trashcan only holds the files... Which is better? Also note that unless explicitely restored, all sorts fstat() info of a file gets messed up because of this (access times, modify times and what have you). Hmm... I'm sorry if this all is beyond the scope of this list. I get carried away easily. Michel.
Has anyone had any problems with MS NT Terminal Server and SAMBA ? Thanks Robert Regional Medical Physics Dept, Middlesbrough UK r.a.royall@iee.org
Re:> Date: Tue, 15 Jun 1999 14:17:29 +0200 > From: "Roth Rainer" <Roth_Rainer@csi.com> > To: <samba@samba.org> > Subject: Inheritage of user rights > > Hello, > > our six W95-clients have access to our Samba 1.9x Server. For the special > directory in question, everybody (owner, group members and other) has full > rights (drwxrwxrwx or 777). > > Now the problem: every user stores files and directories in that main > directory. Unfortunately, ony the owner has full rights, not esp. the other > group members (-rwxr-xr-x). To change the rights by hand is usless (approx. > over 100 files a day). Group members must have full access to the files (the > have to change them). > > So, there is my question: is it possible to inherit the main-directory > rights to every single file and directory to be placed in that main > directory?I have developed a patch for samba 2.0.4b which addresses the general case. It is provisionally called "inherit mode", and if, specified, uses the existing parent directory, rather than the "create mode" parameters, to set permissions on new files and directories. The concept turned out to be straightforward and intuitive and, for us, incredibly useful and beneficial. (We have potentially have 14,000 users and need something for their [homes] share which is simple to specify and understand, yet flexible and effective.) New files inherit the rw bits of the parent directory. New directories inherit all bits (including "t", "g+s") etc. (that is, they clone). For example: We can set up a 711 home directory, and everything the user creates is private (files 600, sub-directories 711). Within that we can set up a "public_html" sub-directory as 755: all user files there are 644. The user may also set up "group" project sub-directories, typically "750 with g+s". [ The reason for 711, not 700, on [homes] is to open it up just enough for the requisite access to things like "public_html". ] I have submitted the patch to the samba people, but no-one has replied!! (Hint!). -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : Phone: +44 191 374 2882 (ddi) South Road : : Fax: +44 191 374 7759 Durham : : Internet: T.D.Lee@durham.ac.uk U.K. :
royall@which.net wrote:> > Has anyone had any problems with MS NT Terminal > Server and SAMBA ?Yes (not me though). Check the list archives for patches, etc... Cheers, jerry ________________________________________________________________________ Gerald ( Jerry ) Carter Engineering Network Services Auburn University jerry@eng.auburn.edu http://www.eng.auburn.edu/users/cartegw "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 )