SCIENTIFIC-LINUX-USERS Archives

May 2015

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Vladimir Mosgalin <[log in to unmask]>
Reply To:
Vladimir Mosgalin <[log in to unmask]>
Date:
Mon, 18 May 2015 14:14:38 +0300
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
Hi Chuck Lane!

 On 2015.05.17 at 14:53:12 -0500, Chuck Lane wrote next:

> between /local-repo/base/nfs-utils-1.3.0-0
> and nfs-utils-1.3.0-0.8, the "nfs.target" file in
> /usr/lib/systemd/system/ was removed.

It's not present in current version, yes.
They changed service files itself so it's not used anymore. There've
been some changes in that area, e.g. there is no explicit need to enable
nfs secure services (gssd, svcgssd), systemd starts them automatically
if needed.

> 
> The effect is that the nfs server does not automatically start 
> after a boot. 
> 
> The simple workaround that I used was to just copy the nfs.target
> file from the older package.

This is wrong workaround. The correct is to remove nfs target from
systemd and enable nfs-server.service

Like, remove all nfs services symlinks from
/etc/systemd/system/multi-user.target.wants/

and do "systemctl enable nfs-server" if you need a server and
"nfs-client" if you need a client.

-- 

Vladimir

ATOM RSS1 RSS2