referring your wiki nas nfs howtos - you seem to suggest editing the /etc/exports file directly. I thought that i've read somewhere that these changes would be overwritten on each reboot of the nas (qnap or synology or both) no? Just wanted to be sure that this would be mentioned on the wiki then ... sorry if it is in already - i just hadn't the time to read it :/

Memphiz Wrote:referring your wiki nas nfs howtos - you seem to suggest editing the /etc/exports file directly. I thought that i've read somewhere that these changes would be overwritten on each reboot of the nas (qnap or synology or both) no? Just wanted to be sure that this would be mentioned on the wiki then ... sorry if it is in already - i just hadn't the time to read it :/

ohhh, I see what you're saying, got it now--thanks for explaining.

No, the changes that need to be made to the Synology /etc/exports file (which do have to be made manually, unfortunately) aren't overwritten on reboot. I'm not sure about the QNAP, but I'd imagine it's the same.

canadave Wrote:ohhh, I see what you're saying, got it now--thanks for explaining.

No, the changes that need to be made to the Synology /etc/exports file (which do have to be made manually, unfortunately) aren't overwritten on reboot. I'm not sure about the QNAP, but I'd imagine it's the same.

Unfortunately not. After a reboot on the QNAP all the changes are lost.

This is a problem because I have automated shutdown every night with a restart each evening.

I already told cranial (who did the qnap wiki entry?) multiple times that this wouldn't happen if he was using "/etc/config/nfssetting" for adding the insecure flag. But he doesn't seem to think so or i just googled wrong. :/

Memphiz Wrote:I already told cranial (who did the qnap wiki entry?) multiple times that this wouldn't happen if he was using "/etc/config/nfssetting" for adding the insecure flag. But he doesn't seem to think so or i just googled wrong. :/

Hey, the important thing is that it's there now Thanks for getting the info in there.

Incidentally, you don't need to put the HTML <br> line breaks throughout the wiki...you can just skip a blank line. Cleaner, easier to read when editing the wiki, etc. I went through and changed it accordingly...also you can sometimes skip two blank lines just to make it a little more readable after graphics. Sometimes there'll be a graphic, an instruction step, and another graphic, and unless you put a couple of blank lines in there, it's unclear which graphic the step is referring to. Check it out and see how I changed it; might make it a little easier on you for next edit.

canadave Wrote:Hey, the important thing is that it's there now Thanks for getting the info in there.

Incidentally, you don't need to put the HTML <br> line breaks throughout the wiki...you can just skip a blank line. Cleaner, easier to read when editing the wiki, etc. I went through and changed it accordingly...also you can sometimes skip two blank lines just to make it a little more readable after graphics. Sometimes there'll be a graphic, an instruction step, and another graphic, and unless you put a couple of blank lines in there, it's unclear which graphic the step is referring to. Check it out and see how I changed it; might make it a little easier on you for next edit.

Ha, I only started using the line breaks as they were in the Synology wiki I shamelessly copied from

Thanks for cleaning it up Canadave. I've cleaned up some errors I made regarding vi that were pointed out, and I've added some external links regarding vi and SSH.

If I have helped you in any way, please forgive me, it was entirely accidental.