Hi all,
We have an NFS server in our env. I was trying to start the service but the service wouldn't start. Later, the one my colleagues noticed it was due to networking=yes in /etc/sysconfig/network. Why would this be the cause? Isn't it a switch for activating network. How's that possible??

networking=yes does NOT prevent NFS from starting so your co-worker appears to be off.

You need to provide more detail such as:
1) Are you talking about NFS server or NFS client or both?
2) What command exactly did you run to "start NFS"?
3) What errors did you get when you ran the command?

Also are you saying removing the line "networking=yes" fixed the problem or is this just an observation he made that it has that?

My colleague just mailed saying "NETWORKING=yes entry was missing from the server" and adding the entry fixed it.

Details:
1. Talking about NFS server only.
2. i used "service nfs start" to start the service.
3. I got no errors when I ran the command, it just gave me no error on stdout; but the exit status 1

I need to try the same at home and check for myself. It doesn't make any sense to me as well.

1 members found this post helpful.

This string checked by lot of init scripts.
No reason to start NFS if server not networked.

[QUOTE=amit.kanade1983;5177929]My colleague just mailed saying "NETWORKING=yes entry was missing from the server" and adding the entry fixed it.

That makes more sense. Clearly if there is no "NETWORKING" then "NETWORK file system" (NFS) shouldn't start.

As the prior poster notes this is checked in the init script for nfs.

On one of my RHEL6 boxes on lines 27 &2 8 of the nfs init script I see:
# Source networking configuration.
[ -f /etc/sysconfig/network ] && . /etc/sysconfig/network

Then later it shows clearly it is checking for the value:
# Check that networking is up.
[ "${NETWORKING}" != "yes" ] && exit 6