fstab, nfs, mount points and rebooting

[elija]

We have added some NFS shares to the fstab and now the server is not rebooting. I don't think the mount points had been created!

Would this stop the server booting?

[Irithori]

Unfortunately, yes.

Your options are: local console, remote management, live cd, ..
and comment the new lines in /etc/fstab
But you know that

[Irithori]

As a further step, a autofs based setup might help:

Roughly like this:
21.2.2.*Mounting NFS File Systems using autofs

a) booting will succeed
b) the mountpoint is only there, if it is needed

[Lakshmipathi]

Yes,I'll second autofs.

[elija]

Unfortunately, yes.

Your options are: local console, remote management, live cd, ..
and comment the new lines in /etc/fstab
But you know that

I was mostly sure but didn't know if adding NFS into the equation would change things; it wasn't the only change made.

Ah well, that means someone gets a day out on Monday.

[elija]

Yes,I'll second autofs.

NFS is only a temporary solution. It is going to be replaced with an incron based system as our other servers are rebuilt.

[Mudgen]

Elija, I've read many of your posts, and learned from you more than once. Having shot dumb holes in my foot more than once, I share your pain and probable embarrassment.

Hope it will make you feel better that I just learned about incron because of this post. Was unaware of it until just now. Lots of possibilities for things I've scripted around my elbow to get to.

[Irithori]

incrond is a start, but the real fun starts with lsyncd

[elija]

Elija, I've read many of your posts, and learned from you more than once. Having shot dumb holes in my foot more than once, I share your pain and probable embarrassment.

Hope it will make you feel better that I just learned about incron because of this post. Was unaware of it until just now. Lots of possibilities for things I've scripted around my elbow to get to.

It's the first time I've done it at work and in fairness, it took two of us to really screw it up

incrond is a start, but the real fun starts with lsyncd

But I understand incron and I've proved it works. I don't want to go through that again

[Irithori]

If it already works, fine

But the basics are the same.
incrond and lsyncd react on fileevents for a given directory.
Such as create, move, delete, etc and can do defineable actions for them.

But incrond only works on one directory level, while lsyncd can monitor recursively.
The possible actions are much more advanced, it is lua based scripting.
Plus, you get
- logging
- queuing before action
- multiple targets
- exclude patterns
- etc

And while the name lsyncd indicates syncing (and yes, this is the primary purpose), lsyncd can trigger arbitrary actions