[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Services can now have a default value
From: |
ng0 |
Subject: |
Re: Services can now have a default value |
Date: |
Wed, 19 Apr 2017 23:22:49 +0000 |
Ricardo Wurmus transcribed 0.9K bytes:
>
> ng0 <address@hidden> writes:
>
> > Before I lock myself out, this is the definition for defaults.
> > So:
> > (service openssh-service-type
> > (openssh-configuration
> > (port-number 12121)))
> >
> > becomes:
> > (service openssh-service-type
> > (port-number 12121))
> >
> > or is this just a definition for defaults and not the configuration, and
> > when the configuration is specified it is still like before this commit?
>
> The “openssh-service-type” has a default value
> “(openssh-configuration)”. If you want to override parts of the default
> configuration you can use the “modify-services” syntax. Your second
> snippet is incorrect, because “service” expects a type and a
> configuration value, but you gave it a type and “(port-number 12121)”,
> which is not a valid configuration.
>
> --
> Ricardo
>
> GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
> https://elephly.net
>
Because I still don't think modify-services is documented well enough
and I have only one case where it's working for me, I assume:
As an example,
(service openssh-service-type
(openssh-configuration
(permit-root-login #t)))
Would still work. If it doesn't, I know there is no lint checking for services
in the system config.
--
PGP and more: https://people.pragmatique.xyz/ng0/
Re: Services can now have a default value, Ricardo Wurmus, 2017/04/17
Re: Services can now have a default value, Carlo Zancanaro, 2017/04/19