systemd: Is it wrong?

Steve Dickson SteveD at redhat.com
Mon Jul 11 01:39:55 UTC 2011



On 07/10/2011 07:31 PM, "Jóhann B. Guðmundsson" wrote:
> On 07/10/2011 11:16 PM, Genes MailLists wrote:
>> On 07/10/2011 07:08 PM, "Jóhann B. Guðmundsson" wrote:
>> ell variables has always had a
>>>> default value of the empty string.)
>>> It achieves afaict the behavior the maintainer wanted if it was up to me
>>> I would have done this ( whole nfs )  completly differently....
>>>
>>> Dropped
>>>
>>> ExecStartPre=/sbin/modprobe -q lockd $LOCKDARG
>>> ExecStartPre=/sbin/sysctl -w $LOCKD_TCPPORT
>>> ExecStartPre=/sbin/sysctl -w $LOCKD_UDPPORT
>>>
>>> Completely and having administrators add and to set these values
>>> manually in /etc/sysctl.conf as I mentioned in comment 30.
>>>
>>    I don't agree with this approach actually. Doing it this way means
>> that we now have dependencies for the daemon spread into non-obvious
>> places not directly associated with starting the daemon.
I do to agree with this... Instead of simply editing one file
/etc/sysconfig/nfs, they know have to edit multiple files
which goes back to my "easy-of-use" argument... Something
that seems to be ignored... 

steved.



More information about the devel mailing list