Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm running my personal computer as a file server on our LAN. Now not all of the users on this LAN run Linux. Several machines are Win XP. I have my system sharing files with write capabilities. But that means that even when a user is browsing the files, XP is allowed to go in and put those pesky thumbs.db files in all my folders. which is just ANNOYING! Now a solution to this, I think is to make the user have read-only privileges unless they intend to write to the drive. thus preventing XP from doing it on it's own.
Now one way I could accomplish this is to change the smb.conf file to allow network logins that aren't local user names. Then have two separate logins. A restricted and a writeable, at least I believe I can do that.
The pain I see in this is that the user would have to know in advance wether they where to write to the drive. because the license seems to stick as long as both the server and the client machine are on the network. therefore changing the log-in because you want to write. then changing back when your done. just seems messy...
What I would prefer is to have the samba login read-only and then if the user attempts to write to the drive, prompt for a write password. then drop back to read mode after write is complete.
Otherwise it would be nice if I could just tell my server to not allow any files to be written with the name "Thumbs.db"
I don't know, but I do know I can't control weather thumbnail caching is enabled on every XP computer my file system comes in contact with, and I am getting tired of deleting the lil' bastards.....
I actually like the Idea of blocking the file name from being created in the system all together, but I have absolutely no idea how to go about doing that. you have any suggestions or maybe some documentation I can follow up on??
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.