<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: Running CIPE from inetd?
From: Martin Buck <mb-list-cipe,AT,gromit,DOT,dyndns,DOT,org>
Date: Mon, 12 Aug 2002 01:45:55 +0200

Hi,

I know that this question has been asked before, but I've not found any
messages indicating success, so here we go again:

Is it possible to run CIPE from inetd? I tried starting it with -i, but
ciped dies immediately after having been started by inetd. This is my
inetd.conf entry:

6900 dgram udp wait root /usr/sbin/ciped ciped -i -o 
/etc/cipe/peers-noauto/wallace-wlan

And this is what ciped says about it in syslog:

Aug 12 01:27:12 gromit kernel: cipcb0: alloc
Aug 12 01:27:12 gromit kernel: cipcb0: setpar
Aug 12 01:27:12 gromit kernel: cipcb0: setpar 0.0.0.0:0 1000 60000 0201 0
Aug 12 01:27:12 gromit kernel: cipcb0: setkey
Aug 12 01:27:12 gromit kernel: cipcb0: attach
Aug 12 01:27:12 gromit inetd[357]: /usr/sbin/ciped: exit status 0x1

This repeats until inetd disables cipe. Here's an strace log of the last
few syscalls:

open("/dev/urandom", O_RDONLY)          = 3
setsockopt(0, SOL_SOCKET, SO_RCVBUF, [65536], 4) = 0
getsockname(0, {sin_family=AF_INET, sin_port=htons(6900),
sin_addr=inet_addr("0.0.0.0")}}, [16]) = 0
ioctl(0, 0x89f4, 0xbffffb84)            = 0
ioctl(0, 0x89f1, 0xbffffb84)            = 0
ioctl(0, 0x89f2, 0xbffffb84)            = 0
ioctl(0, 0x89f3, 0xbffffb84)            = -1 ENOTCONN (Transport endpoint is 
not connected)
write(2, "opendev: attach", 15)         = -1 ENOTCONN (Transport endpoint is 
not connected)
write(2, "\n", 1)                       = -1 ENOTCONN (Transport endpoint is 
not connected)
close(0)                                = 0
_exit(1)                                = ?

Does anybody know what's wrong here?

Thanks,
Martin





<< | Thread Index | >> ]    [ << | Date Index | >> ]