Modify

Opened 10 years ago

Closed 9 years ago

#3449 closed defect (obsolete)

fprobe forked process exits immediately

Reported by: zanchey@… Owned by: developers
Priority: normal Milestone: Kamikaze 7.09
Component: packages Version:
Keywords: Cc:

Description

fprobe 1.1 on Kamikaze 7.09 running on a WRT54G with the 2.4.23 kernel refuses to start correctly. Worked fine in 7.06 on this hardware.

The binary happily prints the usage instructions but when fed a valid set of parameters fails to fork(), or more specifically, the forked child fails to start correctly.

strace output as below:
(strace -f fprobe -i br-lan 192.168.1.5:2055)

sched_get_priority_min(SCHED_FIFO)      = 1
sched_get_priority_max(SCHED_FIFO)      = 99
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
bind(3, {sa_family=AF_UNSPEC, sa_data="\0\0\0\0\0\0\0\0\0\0\0\0\0\0"}, 16) = 0
connect(3, {sa_family=AF_INET, sin_port=htons(2055), sin_addr=inet_addr("192.168.1.5")}, 16) = 0
fork(Process 678 attached
)                                  = 678
[pid   677] exit(0)                     = ?
Process 677 detached
Process 678 detached

The suggestion from my friendly neighbourhood kernel hacker is that it's probably a kernel bug, but he has no idea where to start looking. If there's something more I can do please let me know.

Attachments (0)

Change History (2)

comment:1 in reply to: ↑ description Changed 9 years ago by nico

Replying to zanchey@ucc.gu.uwa.edu.au:

... If there's something more I can do please let me know.

Yes, test with a recent trunk checkout...

comment:2 Changed 9 years ago by nico

  • Milestone set to Kamikaze 7.09
  • Resolution set to obsolete
  • Status changed from new to closed

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.