That's --daylog (which records bytes in/out per day), what you want is
--syslog (which will hopefully record some kind of error, and will end
up in /var/log/messages or similar)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
The child process is expected, it's used for DNS resolution (so as not
to block the main process, which is a select() loop)
Please run with --syslog and see if there's a smoking gun in the logs
when darkstat stops.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I don't think darkstat is the right package, darkstat isn't a GUI app.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964121
Title:
onboard can not type in some input boxes
To manage notifications
Two processes is normal (the child process is to do non-blocking DNS
resolution).
Mytonn is there anything relevant in the syslog?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/249038
Title:
darkst
Glad you got it resolved. ;)
The only other thing I can think of is that it sometimes fails to start
at boot because of an ordering/timing problem (i.e. listening on an
interface before it's up'd). Make darkstat log to syslog, reboot, and
examine the syslog.
--
You received this bug notification
Ok so after boot what does "systemctl status darkstat" say? Because in
#4 it was running with no errors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839492
Title:
Bad test for $START_DARKSTAT in
Apparently "bad" just means it's not a native systemd service.
So it doesn't start on boot? And it doesn't start on "systemctl start
darkstat"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839492
T
What shows up on the console + in "journalctl -f" + in syslog when you
run:
systemctl start darkstat
systemctl status darkstat.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839492
Title:
B
Shouldn't:
test "$START_DARKSTAT" = "yes" || exit 0
Mean "variable has to equal yes or else early exit" ?
$ test "$X" = "yes" || echo early exit
early exit
$ export X=yes; test "$X" = "yes" || echo early exit
$
What am I missing?
--
You received this bug notification because you are a member o
Oh, sorry, which bug should I be following up on?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120
Title:
[SRU] thunar crashes on file renaming
To manage notifications about this bug go to:
ht
Sorry, to be clear: I still see the invalid reads and writes when I'm
dragging and dropping files in the UI.
I tried the loop for renaming files every second and wasn't able to
trigger a crash in thunar with or without the patch.
--
You received this bug notification because you are a member of
Yes, I'm pretty sure I've been able to trigger it with both copy/paste
and drag/drop.
I don't have a reliable way of reproducing it, I manually click around
until I get a crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Created attachment 6636
Use reference counting to avoid crash in deferred reload
I've got a semi-reliable way of triggering this (two side-by-side
windows, showing two different dirs, a lot of image files, drag and drop
and it crashes)
The attached diff increments the refcount before creating the
Copying from https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=800723#96:
This is with thunar-1.6.10: (line numbers will be off because I was
adding debug printfs)
thunar_file_info_reload() touches memory deleted by
thunar_folder_reload()
I don't think this is a thread race because I always see
With Check-if-a-thunar-file-is-still-valid-before-reloading.patch, I
still see the invalid reads and writes, but not the crash on strcmp(NULL
Also, moving ~20 files (drag and drop to another thunar window) feels
very slow now.
--
You received this bug notification because you are a member of Ubu
darkstat v2.x used 666
darkstat v3.x used 667
debianhelp has screenshots from v2.6
My guess is Debian overrode the port to 666 when the package was
upgraded from v2 to v3 so as to not change the (Debian) default. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Great, sounds like the distro part is working correctly! What's left to
do in this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699374
Title:
localhost:666 connection refused error?
To manag
Sorry about the documentation. I can't change what's in that magazine.
:)
The cfg file is specific to the distro and applies to systemd(?)
starting darkstat at boot time, it's not a standard part of darkstat /
not something it reads at startup.
i.e. Either "service start darkstat" or whatever the
The default webserver port should be 667. Try: "netstat -lntp" while
darkstat is running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699374
Title:
connection refused due to pcap error?
To manag
Try: sudo darkstat -i eth0 --debug
The error message could be better, but it's saying there's no interface
called "--debug", which was the argument to -i.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
I can't reproduce the problem with your darkstat + init.cfg files.
I also reverted the darkstat file to the one from the package, and I still
can't reproduce.
Is /bin/sh a symlink to dash?
Please post the output of: ls -l /bin/sh
And also:
/bin/sh -x /etc/init.d/darkstat start
--
You received
> It is failing to start because the -i -p and -b attributes defined in
init.cfg are being overwritten with "" values in the startup script
I'm sorry, I missed this in my first reading.
However, it also doesn't make sense. I just downloaded and unpacked the
package I think you're using:
wget
h
> After configuring /etc/darkstat/init.cfg darkstat still fails to
start, and gives no error or reason why. No logs are generated
Could you please reproduce this with --syslog added to the cmdline flags
and work out why it's failing to start?
--
You received this bug notification because you are
This is driving me nuts. I'm getting it on Debian unstable mousing in
and out of google-chrome. A symptom I'm seeing is that xorg burns a lot
of CPU time while it's happening, it appears to be coming from one of
the closed-source nvidia libraries, and it appears to be issuing a storm
of ioctl()s to
AIUI sdlmess is now a standard part of mess, and there is a much newer
'mess' package in Debian which installs just fine on Ubuntu:
http://packages.qa.debian.org/m/mess.html
Instead of me continuing to maintain my PPA, what do we need to do to
get the upstream mess package into Ubuntu?
--
You re
Good to hear! This will be fixed in the next release (of darkstat)
then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902153
Title:
ubuntu 11.10 darkstat can`t start
To manage notifications about
It took a while to get the binding code right after IPv6 support was
added. Could you please build the latest version from git and tell me
if it still has this problem on your system?
git clone http://unix4lyfe.org/git/darkstat
cd darkstat
# important:
git checkout work
autoconf
autoheader
./conf
Strange. Try specifying the bind address (-b cmdline flag)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902153
Title:
ubuntu 11.10 darkstat can`t start
To manage notifications about this bug go t
Done. This turned out to be pretty easy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/200913
Title:
[needs-packaging] SDLMESS
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
Hi there,
This is my ppa: https://launchpad.net/~darkmoon/+archive/ppa
I have updated the sdlmess therein to 0141 and there's an amd64 build now.
Give it a burl!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Hi all,
Ludomatic did an excellent job packaging this for Debian. I started with
sdlmess_0132 from http://apt.ludomatic.fr/pool/non-free/s/sdlmess/,
bumped the version to 0136, and now have i386 packages in my ppa:
https://launchpad.net/~darkmoon/+archive/ppa
Install:
sudo add-apt-repository ppa:
On Fri, May 07, 2010 at 08:06:24AM -, Jan Cerny wrote:
> Public bug reported:
>
> Binary package hint: darkstat
>
> Ubuntu 10.04 (server) x86_64
> darkstat version 3.0.712-2
> when I start darkstat with /etc/init.d/darkstat start, it listens on port 667
> but when I point my browser there th
Can someone close this bug please?
The problem was due to a botched user edit to init.cfg mostly caused by
bad and confusing commented-out syntax in the default init.cfg, it will
be fixed in the darkstat 3.0.713 package.
--
unable to completely remove darkstat with Synaptic Package Manager
https
If I disable NetworkManager and add e1000 to /etc/modules and configure
eth0 via /etc/network/interfaces, then darkstat starts up just fine (!).
Hew, is your Debian Lenny system using NetworkManager?
Even though it starts up, darkstat 3.0.712-1 on Jaunty can't decode TCP
traffic because of the sna
I can reproduce the problem with darkstat 3.0.712-1 on Jaunty. The
problem is (piping darkstat --verbose --no-daemon through
/usr/bin/logger at boot time):
error: pcap_open_live(): eth0: That device is not up
Changing the boot order via update-rc.d doesn't fix this problem for me.
darkstat nee
I would suggest: http://bazaar.launchpad.net/~darkmoon/+junk/darkstat-
pkg/revision/7
--
unable to completely remove darkstat with Synaptic Package Manager
https://bugs.launchpad.net/bugs/413876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Dustin, the problem is the last line in init.cfg:
DNS="--no-dns" Don't reverse reolve IPs to host names
This is indeed a syntax error in a shell script, and the "unterminated
string" starts at the single quote in "don't" ;)
No offense intended, but I believe this is user error, and not really a
The commented out #DNS line in the default init.cfg file is bad. This
should be fixed in the package.
--
unable to completely remove darkstat with Synaptic Package Manager
https://bugs.launchpad.net/bugs/413876
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Dustin, could you please post your /etc/darkstat/init.cfg?
--
unable to completely remove darkstat with Synaptic Package Manager
https://bugs.launchpad.net/bugs/413876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
The relevant part of the dpkg log:
Setting up darkstat (3.0.712-1) ...
[33m*[39;49m please change the value of START_DARKSTAT in order to
start darkstat
Log ended: 2009-08-14 23:35:34
Log started: 2009-08-15 07:20:29
(Reading database ... 126336 files and directories currently installed.)
40 matches
Mail list logo
