From: Francesco Paolo Lovergine <france...@lovergine.com>
Subject: Re: Bug#987920: ypbind-mt: /etc/defaultdomain should be created at 
installation time
Date: Sun, 02 May 2021 08:48:06 +0200

> Indeed, the general NIS howto included in the nis package provides the full 
> documentation for who upgrades
> or install both servers and clients. A small per program README could 
> probably be a good idea for minimal
> setup. My original idea was having the nis package as a doc only package 
> after bullseye. It is now a
> migration package, instead. Well, I think that a simple README file could be 
> added at this stage of
> release...

Though it doesn't cause problem for me, I have an unanswered question
about setting of this packages.

----------------------------------------------------------------------
yasu@rolling-vm-debian1[1030]% cat /lib/systemd/system/ypbind.service
[Unit]
Description=NIS Binding Service
Requires=rpcbind.service
Wants=network-online.target
After=network-online.target rpcbind.service
Before=systemd-user-sessions.service
Before=nss-user-lookup.target

[Service]
Type=forking
PIDFile=/run/ypbind.pid
Environment=YPBINDARGS=
EnvironmentFile=-/etc/default/nis
ExecStartPre=/bin/domainname -F /etc/defaultdomain
ExecStart=/usr/sbin/ypbind $YPBINDARGS

[Install]
WantedBy=multi-user.target
yasu@rolling-vm-debian1[1030]%
----------------------------------------------------------------------

According to the unit file of ypbind.service, the value of YPBINDARGS
environment variable is passed as arguments when systemd starts ypbind
process. Then how does user set it if he wants to start ypbind with
arguments? As far as I see the unit file this package doesn't seem to
provide the way to set it. I'm not familiar with systemd but does
systemd itself provide such functionality?

Reply via email to