Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
Is there any way to know who deleted samba share dir/file?
I have running samba server on FC7 machine, and my user machine is windows.
It depends....was it deleted from a Windows workstation, or from the Linux system?
From Windows, you could always go check the recycle bin's on different folks desktops, and see if your folder is there. From Linux, check the shell history files of the different users, and see if there's someone who deleted it.
If you have a publicly writable share, you should use "security = user" instead of "security = share", which is obsolete, so each user needs to authenticate. Also set the "sticky" bit on the directory being shared. That prevents one user from deleting another users files inside the directory. It is still up to the user saving a file to modify the write permissions of the file to prevent other users from altering or zeroing the file.
You could enable auditing in the kernel. The filesytem you use would need to support it.