All new accounts created on Gitlab now require administrator approval. If you invite any collaborators, please let Flux staff know so they can approve the accounts.

Commit b2b26482 authored by Mike Hibler's avatar Mike Hibler

Mountd strikes again! The BSD mount command sends a HUP to mountd every

time it successfully mounts a filesystem.  Since we mount about 80 gazillion
filesystems in jails and these mounts are overlapped with other parts of the
setup process, it is quite likely that some jail's innocent use of
/usr/bin/foo is going to be blown out of the water by a random senseless HUP.

Grisly hack: when setting up jails, rename mountd.pid so mount can't find it.
Hah! hup THIS mount!
parent 1f031f4f
......@@ -246,6 +246,16 @@ for (my $i = 0;
system("sysctl net.inet.ip.intr_queue_maxlen=128 >/dev/null 2>&1");
system("sysctl vfs.nfs.eacces_retry_enable=1 >/dev/null 2>&1");
#
# XXX grossed out yet? Try this one: the mount command will HUP mountd
# after every successful mount. Thus if mounts in one jail overlap NFS
# activity in another, the latter may be randomly killed off.
#
# Elegant solution: rename the mountd.pid file so mount cannot find it!
#
rename("/var/run/mountd.pid", "/var/run/mountd.thisreallysux")
if (-e "/var/run/mountd.pid");
foreach my $vnode (sort(keys(%newvnodelist))) {
# Blocks until mostly setup.
bootvnode($vnode, "boot", $newvnodelist{$vnode});
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment