Re: rbootd will nicht rbooten

On Sun, Nov 24, 2002 at 02:42:34PM +0100, Oliver Lehmann wrote:
> Bernd Walter wrote:
>
> >
> > Achte auf den RetCode:
> > #define RMP_E_NOFILE 16 /* boot reply: file does not exist */
> > Laut soruce versucht der einen open(2) auf das File - sollte per
> > ktrace/kdump leicht zu prüfen sein, was für einen Pfad der genau sucht.
>
> 210 rbootd CALL write(0x1,0x8053000,0x3a)
> 210 rbootd GIO fd 1 wrote 58 bytes
> "<<< 14:23:45.936469 Addr: 08:00:09:70:69:21 Intf: ep0
> "
> 210 rbootd RET write 58/0x3a
> 210 rbootd CALL write(0x1,0x8053000,0x25)
> 210 rbootd GIO fd 1 wrote 37 bytes
> " 802.2 LLC: DSAP:f8 SSAP:f8 CTRL:300
> "
> 210 rbootd RET write 37/0x25
> 210 rbootd CALL write(0x1,0x8053000,0x20)
> 210 rbootd GIO fd 1 wrote 32 bytes
> " HP Ext: DXSAP:608 SXSAP:609
> "
> 210 rbootd RET write 32/0x20
> 210 rbootd CALL write(0x1,0x8053000,0xf)
> 210 rbootd GIO fd 1 wrote 15 bytes
> " Boot Request:
> "
> 210 rbootd RET write 15/0xf
> 210 rbootd CALL write(0x1,0x8053000,0x2b)
> 210 rbootd GIO fd 1 wrote 43 bytes
> " RetCode:0 SeqNo:2e943658 SessID:0 Vers:2
> "
> 210 rbootd RET write 43/0x2b
> 210 rbootd CALL write(0x1,0x8053000,0x25)
> 210 rbootd GIO fd 1 wrote 37 bytes
> " Machine Type: HPS700
> "
> 210 rbootd RET write 37/0x25
> 210 rbootd CALL write(0x1,0x8053000,0x14)
> 210 rbootd GIO fd 1 wrote 20 bytes
> " File Name (0): <>
> "
> 210 rbootd RET write 20/0x14
> 210 rbootd CALL write(0x1,0x8053000,0x1)
> 210 rbootd GIO fd 1 wrote 1 byte
> "
> "
> 210 rbootd RET write 1
> 210 rbootd CALL sigprocmask(0x3,0xbfbff3a0,0xbfbff390)
> 210 rbootd RET sigprocmask 0
> 210 rbootd CALL sigprocmask(0x1,0xbfbff3d0,0xbfbff3c0)
> 210 rbootd RET sigprocmask 0
> 210 rbootd CALL gettimeofday(0xbfbfe598,0)
> 210 rbootd RET gettimeofday 0
> 210 rbootd CALL break(0x8056000)
> 210 rbootd RET break 0
> 210 rbootd CALL getpid
> 210 rbootd RET getpid 210/0xd2
> 210 rbootd CALL sendto(0x2,0xbfbfea40,0x4d,0,0,0)
> 210 rbootd GIO fd 2 wrote 77 bytes
> "<30>Nov 24 14:23:45 rbootd[210]: 08:00:09:70:69:21: request to
> boot (denied)"
> 210 rbootd RET sendto 77/0x4d
> 210 rbootd CALL gettimeofday(0x8054df0,0)
> 210 rbootd RET gettimeofday 0
> 210 rbootd CALL sigprocmask(0x1,0xbfbff210,0xbfbff200)
> 210 rbootd RET sigprocmask 0
>
> [...]
>
> denied? wiso das denn? die ip adresse taucht in rbootd.conf auf, und das
> SYSNBSD versucht er ja nichtmal zu oeffnen. (zumindest aber findet er es
> oben beim getdirentries()).

Die Ausgabe unterscheided sich auch von der, die du Ursprünglich
gemailed hast.

> am anfang kommt komischerweise auch 953 mal
>
> 210 rbootd CALL close(0x3)
> 210 rbootd RET close -1 errno 9 Bad file descriptor
> 210 rbootd CALL close(0x4)
> 210 rbootd RET close -1 errno 9 Bad file descriptor
> 210 rbootd CALL close(0x5)
> 210 rbootd RET close -1 errno 9 Bad file descriptor
> [...]
> 210 rbootd CALL close(0x3bc)
> 210 rbootd RET close -1 errno 9 Bad file descriptor

Ighhh - schätze ein antikes Relikt aus der pre close-on-exec Zeit.
Sollte man evtl rauswerfen, ist aber harmlos.

-- 
B.Walter              COSMO-Project         http://www.cosmo-project.de
ticso(at)cicely.de         Usergroup           info(at)cosmo-project.de
To Unsubscribe: send mail to majordomo(at)de.FreeBSD.org
with "unsubscribe de-bsd-questions" in the body of the message