2.4exp

[Michal Moskal]

On Mon, May 20, 2002 at 10:13:14AM +0200, Blues wrote:
> On Sat, 18 May 2002, Michal Moskal wrote:
> > > Przy instalacji z dzisiejszego bootdisk_net po sieci jest taki
> > > kwiatek, że najpierw instalator odpala dhcpcd, zasysa jakieś tam
> > > pliczki bazowe, moduły scsi itp, a potem próbuje po raz drugi odpalić
> > > dhcpcd i instalka wywala się na ryjek z tekstem:
> > > 
> > > *** dhcpcd: already running
> > > *** dhcpcd: if not then delete /var/run/dhcpcd-eth0.pid
> > > 
> > > dhcpcd pracuje.
> > > 
> > > Może 
> > > if [ ! -f /var/run/dhcpcd-ethX.pid ]; then
> > >   dhcpcd...
> > > fi
> > > ?
> > 
> > Może raczej 
> > 
> > kill `cat /var/run/dhcpcd*`
> > rm -f /var/run/dhcpcd*
> > sleep 1
> > dhcpcd?
> 
> 
> Nie.
> 
> Fragment z manuala dhcpcd:
> 
> -k     Sends  SIGHUP  signal  to  the  dhcpcd process that is 
>        currently running. If dhcpcd receives SIGHUP it will send 
>        DCHP_RELEASE message to the server and destroy dhcpcd cache. 
>        In  a  case dhcpcd  receives  SIGTERM  which  is  normally 
>        used by shutdown(8) when rebooting the system dhcpcd will 
>        not send DHCP_RELEASE and will not destroy cache. When system 
>        boots dhcpcd  will use cache to request the same IP address 
>        from DHCP server which was assigned before the system went down.
> 
> -n     Sends SIGALRM signal to the dhcpcd process that is currently 
>        running which forces dhcpcd  to try to renew the lease. If 
>        dhcpcd is not running, the flag is ignored and dhcpcd follows the
>        normal startup procedure.
>

Kiedy nam wcale nie przeszkadza, że dostanie to samo IP, bardzo dobrze,
że tak się stanie. 


-- 
: Michal Moskal ::::: malekith/at/pld-linux.org :  GCS {C,UL}++++$ a? !tv
: PLD Linux ::::::: Wroclaw University, CS Dept :  {E-,w}-- {b++,e}>+++ h