Modify

Opened 10 years ago

Closed 10 years ago

#2885 closed defect (fixed)

darkstat - init scripts are wrong and application does not start

Reported by: michu-at-neophobdotcom Owned by: developers
Priority: normal Milestone:
Component: packages Version:
Keywords: Cc:

Description

The new darkstat package suffers from 2 errors:

1) Wrong init script:

Index: darkstat.init
===================================================================
--- darkstat.init       (revision 9872)
+++ darkstat.init       (working copy)
@@ -22,7 +22,7 @@
        scan_interfaces
        config_get ifname "$interface" ifname

-       $BIN -d -i "${ifname:-$interface}" \
+       $BIN --debug -i "$interface" \
                ${httpaddr:+-b "$httpaddr"}  \
                ${httpport:+-p "$httpport"}
 }

2) The application does not work, I receive a bogus error message (tried with various interfaces)

root@OpenWrt:~# darkstat --debug -i br-lan
darkstat 3.0.707 (built with libpcap 2.4)
darkstat (00706): starting up
darkstat (00707): set uid/gid to 65534/65534
darkstat (00707): DNS child entering main DNS loop
darkstat (00707): entering blocking read loop
darkstat (00706): DNS child has PID 707
darkstat (00706): caplen is 54
darkstat (00706): capturing in promiscuous mode
darkstat (00706): listening on 0.0.0.0:667
darkstat (00706): loaded 45 protos
darkstat (00706): loaded 1 tcp and 1 udp servs, from total 2
  706: error: chdir("yes") failed: No such file or directory

Attachments (1)

darkstat_2885.patch (1.5 KB) - added by anonymous 10 years ago.

Download all attachments as: .zip

Change History (3)

comment:1 Changed 10 years ago by florian

Init script fixed with [10064], thanks !

Changed 10 years ago by anonymous

comment:2 Changed 10 years ago by florian

  • Resolution set to fixed
  • Status changed from new to closed

Applied in [11915], thanks !

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.