troubleshooting:mountall
                Differences
This shows you the differences between two versions of the page.
| troubleshooting:mountall [2010/03/10 13:59] – created jas | troubleshooting:mountall [2010/03/12 16:04] (current) – jas | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== mountall ====== | ====== mountall ====== | ||
| + | Initially, before experimenting with autofs, I placed all the mounts in /etc/fstab. | ||
| + | When the system would boot up, /obj/cse would be mounted, /obj/home9, and / | ||
| - | sigh .. all of this needs to be reworked.. more later. | + | The developer fixed the bug supposedly in Lucid (10.04), but did not bother fixing it in Karmic (9.10) for which we are basing our test environment! | 
| - | + | ||
| - | When the system would boot up, /obj/cse would be mounted, /obj/home9, and / | + | |
| - | + | ||
| - | dual problem... | + | |
| - | - odd time, mountall | + | |
| - | + | ||
| - | - sends a SIGUSR1 every time network interface is mounted, but we only want it to try moutning NFS when say, tun0 is mounted | + | |
| - | - then we have the secondary problem that it doesn' | + | |
| - | + | ||
| - | + | ||
| - | < | + | |
| - | + | ||
| - | </ | + | |
| Bug report from Launchpad: | Bug report from Launchpad: | ||
| Line 22: | Line 10: | ||
| https:// | https:// | ||
| + | Note:  to debug mountall, insert into / | ||
| - | To debug mountall, insert into / | ||
| - | |||
| - | When the network interface comes up, the system sends SIGUSR1 to the mountall process (/ | ||
troubleshooting/mountall.1268247568.txt.gz · Last modified:  by jas
                
                