Can I ignore any or all of the following, or what should I do about
them?
During bootup:
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: recovery directory /var/lib/nfs/v4recovery doesn't exist
NFSD: starting 90-second grace period
If I make the directory it wants, the warning goes away. I don't notice
any difference in operations with or without it, and I don't know what
ownership or permissions should be applied to the directory, anyway.
On a system without volume groups, I see the following:
Setting up Logical Volume Management: /var/lock: mkdir failed: Read-only file system
No Volume groups found
[ OK ]
I assume this is unimportant (seeing as there's no LVMs on that system),
but why's it trying to make a directory in /var before /var is mounted
(or mounted as writeable)?
On another system with volume groups there is no such warning, I see two
volume groups being successfully mounted. Though, yet again, this
procedure occurs before I expect volumes/partitions to be mounted as
writeable.
On shutdown:
Unmounting NFS filesystem: [ OK ]
Stopping NFS locking: [FAILED]
Stopping NFS statd: [ OK ]
Is that failure worth worrying about? Is there anything I can do about
it?
NB: These errors all occur on systems that have been set up by the
installer (i.e. no user tampering has happened, yet). They still occur
after all updates have been applied. And they're on systems with and
without SELinux enabled.
--
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
--
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
