> So we have 2 options: > > using TERM we get rid of udhcpc.pid but not of > /etc/resolvconf/run/interface/eth0.udhcpc
Actually, TERM should probably call the deconfig script. The only problem is that changing the behavior would probably change a number of peoples configurations. The issue is that a SIGTERM doesn't necessarily mean the user wants their connection severed. > using SIGUSR2 we get rid of /etc/resolvconf/run/interface/eth0.udhcpc > but not of udhcpc.pid If you want the connection to come down, then the documented behavior is to give a SIGUSR2 and then if you want it to die, a SIGTERM. > Is there a third way ? Do you have any suggestion ? I would give a SIGUSR2 and then a SIGTERM, you don't need a delay between the signals. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
