*nix Thread, Locking the filesystem? in Technical; So, I've created an install of Debian which runs a python script after auto-login which wraps around FreeRDP to allow ...
11th January 2013, 11:05 AM #1
Locking the filesystem?
So, I've created an install of Debian which runs a python script after auto-login which wraps around FreeRDP to allow kids to log in with it using NLA (allowing our load balancer to work right).
Now, I've got everything working as I want except a single feature - I want the disk to basically be locked. I know I could get it to mount everything read-only, but I suspect this will just cause everything to spew nonsense at the user when they turn on the machine.
How do I go about making it 'locked' so that var doesn't fill up with logs etc...? HP managed it with their ThinPro system somehow.
I don't really care about logs etc... because if there is an issue, it'll just get reimaged back to the base image.
IDG Tech News
11th January 2013, 12:44 PM #2
I wouldn't worry about the logs - Linux is designed to be on forever and rotates them peridically, throwing away the oldest ones. If you're really worried, put /var on a different partition.
11th January 2013, 12:47 PM #3
Could you replace the log files in var with symbolic links to /dev/null?
Originally Posted by localzuk
11th January 2013, 12:49 PM #4
It does cause disk access though, which might wear down a (cheaper / older) SSD or similar.
Originally Posted by mats
11th January 2013, 01:02 PM #5
If you don't want the user to alter files, just don't give them write access to their home dir. If you want it to restore to a known state on logout/reboot, perhaps the way live CDs work, loopback a ram FS
18th January 2013, 10:16 PM #6
You could base the solution on Debian Live instead. This gives you hooks at various stages to configure the system and user for a live session. Locally installed or network boot it...
19th January 2013, 01:10 AM #7
I've read and re-read your post - could you explain a bit further because I don't understand why you want the disk read-only.
Originally Posted by localzuk
Have you thought about deleting profiles on login and just recreating them them from /etc/skel or am I on a different line from your thinking?
19th January 2013, 11:55 AM #8
Basically, the disk is 1GB in size. After full setup, it has 45MB of space left. I don't want to hit issues where the log files grow and fill the disk. So, I want the disk locked so on reboot, there is still 45MB space left - meaning that even if the disk fills up in a session for whatever reason, a reboot will resolve it.
19th January 2013, 12:35 PM #9
understood. I think @dhicks is on the right lines with redirecting to /dev/null in your /etc/rsyslog.conf
By El_Nombre in forum How do you do....it?
Last Post: 3rd May 2011, 05:17 PM
By theeldergeek in forum Jokes/Interweb Things
Last Post: 18th May 2010, 09:09 PM
By DaveP in forum Downloads
Last Post: 23rd February 2010, 08:59 AM
By tosca925 in forum Windows
Last Post: 17th January 2006, 06:13 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)