> Frank,
> Do I have to re-post my patches or can they go into rc5 ?
They should be good for rc5, if you can rebase them that would be handy, but
they should apply ok.
Just waiting for review from Malahal and/or Swen.
Frank
> From: "Frank Filz"
> To:
Frank,
Do I have to re-post my patches or can they go into rc5 ?
Marc.
From: "Frank Filz"
To:
Date: 05/05/2017 04:47 PM
Subject:[Nfs-ganesha-devel] Announce Push of V2.5-rc4
Branch next
Tag:V2.5-rc4
NOTE:
Branch next
Tag:V2.5-rc4
NOTE: This merge has an ntirpc pullup - please update your submodule
Release Highlights
* fix various races and issues with exports and mdcache, esp. unexport
* make sure rename and link check handles for different exports (XDEV)
* Fix infinite loop in
It seems my spec file was not correct. Hence, nfs-ganesha service was not
getting installed as ganesha at
/etc/sysconfig.
It was a bit confusing because of two different names: nfs-ganesha and ganesha.
--
Supriti Singh��SUSE Linux GmbH, GF: Felix Imend��rffer, Jane Smithard, Graham
FWIW, we should probably rename scrips/sysconfig/nfs-ganesha to
scripts/sysconfig/ganesha, since the .spec file renames it on install,
and it bit someone here trying to generate .debs.
Daniel
On 05/05/2017 10:44 AM, Soumya Koduri wrote:
>
>
> On 05/05/2017 07:04 PM, Supriti Singh wrote:
>>
>From Matt Benjamin :
Matt Benjamin has uploaded this change for review. (
https://review.gerrithub.io/359858
Change subject: dispatch: call SVC_STAT before svcerr_*
..
dispatch: call SVC_STAT before
On 05/05/2017 07:04 PM, Supriti Singh wrote:
> Hello,
>
> In the file scripts/systemd/nfs-ganesh.service the EnviromentFile
> expected is named "ganesha". But the file in systemd/sysconfig is named
> "nfs-ganesha". Is it intentional?
>
yes. That file gets generated at runtime by