[gpfsug-discuss] What happened to /usr/bin/ganesha.nfsd in 5.0.1-0??

[Malahal R Naineni]

The systemd service file also was updated to account for the daemon binary 
rename (the rename itself was done to avoid SELinux issues). It is 
possible that the systemd was using an old cache (unlikely as I didn't see 
daemon-reload message here) or the rpm update couldn't update the file as 
user changed the systemd unit service file (most likely case here).

Please provide "rpm -qV <ganesha-rpms>", the RPM shipped unit file should 
NOT have any reference to ganesha.nfsd (it should have gpfs.ganesha.nfsd). 
 

Regards, Malahal.
PS: No symlink magic is necessary with usual cases!



From:   Jonathan Buzzard <jonathan.buzzard at strath.ac.uk>
To:     gpfsug-discuss at spectrumscale.org
Date:   05/16/2018 12:01 AM
Subject:        Re: [gpfsug-discuss] What happened to 
/usr/bin/ganesha.nfsd in 5.0.1-0??
Sent by:        gpfsug-discuss-bounces at spectrumscale.org



On 15/05/18 19:08, Bryan Banister wrote:
> BTW, I just tried the symlink option and it seems to work:
> 
> # ln -s gpfs.ganesha.nfsd ganesha.nfsd
> 
> # ls -ld ganesha.nfsd
> 

Looks more like to me that the systemd service file needs updating so 
that it exec's a file that exists. One wonders how this got through QA 
mind you.

JAB.

-- 
Jonathan A. Buzzard                         Tel: +44141-5483420
HPC System Administrator, ARCHIE-WeSt.
University of Strathclyde, John Anderson Building, Glasgow. G4 0NG
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20180516/3ebf04f6/attachment.htm>