dhcpcd procedure

1999-10-01 Thread Dpk
I recently adopted dhcpcd... previous versions of dhcpcd would restart during upgrades, which obviously is bad for those doing it remotely. Since my recent upload does not restart dhcpcd, I need to start it for those upgrading from previous versions that did stop the daemon. What would be the be

Re: dhcpcd procedure

1999-10-01 Thread Edward Betts
Dpk <[EMAIL PROTECTED]> wrote: > What would be the best way to check for this? A simple 'ps |grep > dhcpcd' ? Would doing so make my package dependent on procps? or is > there a convenient way to check the installed version of dhcpcd > someway? Check $2 Debian Packagin

Re: dhcpcd procedure

1999-10-01 Thread Wichert Akkerman
Previously Edward Betts wrote: > Check $2 No, check $1. Wichertk -- == This combination of bytes forms a message written to you by Wichert Akkerman. E-Mail: [EMAIL PROTECTED] WWW: http://www.wi.leidenuniv.nl/~wichert/

Re: dhcpcd procedure

1999-10-02 Thread Josip Rodin
On Fri, Oct 01, 1999 at 12:28:36PM -0400, Dpk wrote: > I recently adopted dhcpcd... previous versions of dhcpcd would restart > during upgrades, which obviously is bad for those doing it remotely. > Since my recent upload does not restart dhcpcd, I need to start it for > those upgrading from previo

Re: dhcpcd procedure

1999-10-02 Thread Steve Greenland
On 01-Oct-99, 11:28 (CDT), Dpk <[EMAIL PROTECTED]> wrote: > What would be the best way to check for this? A simple 'ps |grep > dhcpcd' ? Would doing so make my package dependent on procps? or is > there a convenient way to check the installed version of dhcpcd > someway? As others have said, ch