Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
ok, have samba serving a few access databases. the issue is that whenever the first user logs on access creates a lock file and gives them the only write permission, thus preventing other users from writing to the lock file and denying them acess. How can i have this file writeable by all users every day. I have been chmoding them every morning when the first user logs on, roughly 9:00 and am getting tired of doing this. TIA
even when i set the directory permissions for 777 ( bad, I know) the new file is not writable by others ( which it absolutely has to be). No, they are not in the same group, as this particular server needs to have the highest standard of security for PHI (protected health information). Just another thing to point out in our audits....... so i cant really do that.... looking for another workaround.
actually, MS ACCESS can handle quite a few users. The lock files are there to ensure that any given record is being edited by a single user at one time just as in MYSQL, and PostgreSQL. Thanks for the effort, but no.