I don't know anything about a sandbox script. Assuming this is otherwise a normal install, just to be safe, I would:
1. reboot into level 1 (single user mode); 2. Edit /etc/fstab and comment out the /tmp line. 3. Reboot normally. That should take are of it. Previous disk space caveats apply. How much space do you have on / ? (Run "df -hP /" to find out.) ________________________________ From: owner-scientific-linux-us...@listserv.fnal.gov <owner-scientific-linux-us...@listserv.fnal.gov> on behalf of Francesco Alfano <00000bdf64e162f4-dmarc-requ...@listserv.fnal.gov> Sent: Wednesday, April 29, 2020 12:09 To: ONeal, Miles <00000be99a30c213-dmarc-requ...@listserv.fnal.gov>; scientific-linux-us...@listserv.fnal.gov <scientific-linux-us...@listserv.fnal.gov>; jm...@st-andrews.ac.uk <jm...@st-andrews.ac.uk> Subject: Re: [SCIENTIFIC-LINUX-USERS] Why /tmp is bound in /tmp ? How can I remove this bound Caution: EXTERNAL email Now I don't have access to the pc and therefore I can't try, so I had to wait until tomorrow. To permanently remove the mount of / tmp on / tmp, is it sufficient to avoid starting the "sandbox" init script? That is, since it is not used, can I uninstall the sandbox? In this case what are the rpm to be removed? Il mercoledì 29 aprile 2020, 18:58:53 CEST, ONeal, Miles <00000be99a30c213-dmarc-requ...@listserv.fnal.gov> ha scritto: The mount points are set up that way so that filling up one of them doesn't keep the others from being written to. This helps protect from data loss. If the system is quiescent, you might be able to just unmount /tmp . If you need something copied from there, just remount it temporarily on a dir you create (such as /tmp_old ) and copy it. This assumes you have plenty of space on . BUT... this means that if something fills up /tmp/ your system is probably hosed until you reboot. Is there no way you can rebuild that old executable? Someone made a really [poor decision in depending on /tmp to be on / . Otherwise, your best bet is to reinstall and use a custom disk partition setup. But the above caveats about /tmp filling up will still apply. ________________________________ From: owner-scientific-linux-us...@listserv.fnal.gov <owner-scientific-linux-us...@listserv.fnal.gov> on behalf of Jose Marques <jm...@st-andrews.ac.uk> Sent: Wednesday, April 29, 2020 11:46 To: <scientific-linux-us...@listserv.fnal.gov> <scientific-linux-us...@listserv.fnal.gov> Subject: Re: [SCIENTIFIC-LINUX-USERS] Why /tmp is bound in /tmp ? How can I remove this bound Caution: EXTERNAL email > On 29 Apr 2020, at 15:49, Francesco Alfano > <00000bdf64e162f4-dmarc-requ...@listserv.fnal.gov> wrote: > > Why /tmp is bound on /tmp ? (also /home on /home, /var/tmp on /var/tmp) Interesting, one of the last SL6 VMs we have doesn't do this. The (/etc/init.d/sandbox) has mount commands that setup bind mounts for /tmp etc. The comments in the script say: # description: sandbox, xguest and other apps that want to use pam_namespace \ # require this script be run at boot. This service script does \ # not actually run any service but sets up: \ # /var/tmp, /tmp and home directories to be used by these tools.\ # If you do not use sandbox, xguest or pam_namespace you can turn \ # this service off.\ # No idea if this is related. The University of St Andrews is a charity registered in Scotland, No. SC013532.
