dhcpcd-discuss

Dammit!

So the only platform where we actually know the PID of the process which 
requested the deletion is NetBSD-current (which is ironically my main 
dev platform). All other platforms either don't have it in the structure 
sent back (all other BSD's) or it's zero (Linux, from the kernel).

So sadly my patch is of no help :(

Roy

On 19/03/2018 22:59, jobhunts02@xxxxxxx wrote:
> I tried your patch and always get a pid of 0.  Is that expected behavior?
>
> Thank you.
>
>
> -----Original Message-----
> From: Roy Marples <roy@xxxxxxxxxxxx>
> To: jobhunts02 <jobhunts02@xxxxxxx>; dhcpcd-discuss 
> <dhcpcd-discuss@xxxxxxxxxxxx>
> Sent: Tue, Mar 6, 2018 1:06 am
> Subject: Re: [dhcpcd-discuss] Addresses not deleted when cable pulled
>
> On 06/03/2018 02:43, jobhunts02@xxxxxxx <mailto:jobhunts02@xxxxxxx> wrote:
>  > Thankyou very much for that information.  I do not have to pull the
>  > cable to see the "deleted" message in dhcpcd.log.
>  >
>  > On another run, in /var/log/messages:
>  > Mar  6 02:14:59 2018 4550V2 ntpd[7371]: Deleting interface #3 eth1,
>  > 192.168.2.150#123, interface stats: received=0, sent=0, dropped=0,
>  > active_time=4 secs
>  >
>  > This occurs before the dhcpcd.log shows it was deleted:
>  > Mar 06 02:15:17 [6615]: eth1: deleted IP address 192.168.2.150/24
>  >
>  > I will look into why this 3rd party software deleted it.
>
> To make life easier I added this patch:
> https://roy.marples.name/git/dhcpcd.git/commit/?id=c8d1a4150812b2d01c9cc2e5272a2ba19bc0196f
>
> Now, the process id which deleted the address will be logged.
>
> Good luck!
>
> Roy