I'm assuming not in 2.5.0, since that's due out this week. So 2.6-dev,
but if we get the compatibility right, I see no reason why it can't be
backported to 2.5.x. (or maybe even 2.4.x if necessary...)
Daniel
On 05/23/2017 08:26 AM, supriit singh wrote:
> I was talking about the file
I was talking about the file /etc/sysconfig/ganesha. In SUSE packaging,
generally service file is expected to be same as package name. So, to
use "ganesha" is a bit problematic.
Other than that, I think only logs are using the name "ganesha". As
discussed in last concall, the only issue with
I think Supriti is talking about the sysconfig file, which is installed
by nfs-ganesha.spec-in.cmake as /etc/sysconfig/ganesha
Daniel
On 05/16/2017 10:45 AM, Kaleb S. KEITHLEY wrote:
> On 05/16/2017 10:15 AM, Supriti Singh wrote:
>> I have another question. Why are we using the name "ganesha"
On 05/16/2017 10:15 AM, Supriti Singh wrote:
> I have another question. Why are we using the name "ganesha" and not the
> package name "nfs-ganesha" for the service file.
> It may happen that there is another package named "ganesha" (not yet but
> a possibility).
> Also, it will be better to
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:
>>
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
