1 |
On 2022-10-19, Michael <confabulate@××××××××.com> wrote: |
2 |
> On Wednesday, 19 October 2022 01:00:31 BST Grant Edwards wrote: |
3 |
>> On 2022-10-18, Grant Edwards <grant.b.edwards@×××××.com> wrote: |
4 |
>> |
5 |
>> Why would dhcpcd have the persistent option enabled by default? |
6 |
> |
7 |
> I think because this causes less breakage in those cases where netmount, |
8 |
> remote syslog-ng, SSH clients, or root mounted NFS is in play? This is what |
9 |
> the man page says about it: |
10 |
> |
11 |
> "... dhcpcd normally de-configures the interface and configuration when it |
12 |
> exits. Sometimes, this isn't desirable if, for example, you have root mounted |
13 |
> over NFS or SSH clients connect to this host and they need to be notified of |
14 |
> the host shutting down." |
15 |
|
16 |
I guess that makes sense. What was confusing was that I read the man |
17 |
page which said it was normally disabled, and since I had never |
18 |
touched the config file, and wasn't passing the -p option I assumed it |
19 |
was disabled -- then I finally looked through the default config file, |
20 |
where it's "nomrally enabled". |
21 |
|
22 |
-- |
23 |
Grant |