Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a Samba server running on RH 9, and everything is fine except for this one thing. After a few days, the windows clients can only open their files in read-only mode. I have a public shared folder, with each users subfolder, and all belong to group root, and all the users belong to group root.
If I go in and do a chgrp to root for the public folder, and chmod 777, all the files are accessible for a few days, then slowly the problem re-appears.
Any ideas? and do I need to give more info? Thanks!!
One option would be: In the smb.conf file, add a line like this: force user = {the user who owns the file}.
Esentially what you're telling Samba is, "No matter who connects, act as though they are {}." So, if you're sharing a folder that is owned by, let's call him Joe Blow, then Samba will act as though Joe signed in, authenticated and is currently accessing the share.
I don't advise you do this with root (as that is always a bad idea--security wise). But, if Root owns the folder, either change it, or go with it.
Originally posted by issinho One option would be: In the smb.conf file, add a line like this: force user = {the user who owns the file}.
Esentially what you're telling Samba is, "No matter who connects, act as though they are {}." So, if you're sharing a folder that is owned by, let's call him Joe Blow, then Samba will act as though Joe signed in, authenticated and is currently accessing the share.
I don't advise you do this with root (as that is always a bad idea--security wise). But, if Root owns the folder, either change it, or go with it.
Thanks! Point well taken about Root, but I will give this a try.
Originally posted by mpeg4codec Make sure you set the create mode to something like 666. In Samba, you would add something like this to the share's definition:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
