This bug was fixed in the package ntop - 3:4.0.3+dfsg1-2
---
ntop (3:4.0.3+dfsg1-2) unstable; urgency=low
[ Ludovico Cavedon ]
* Rename maintainer scripts including the package name.
* Remove misplaced ru.po file.
* Add Vcs-* headers.
* Do not call netstat, but read interfac
** Branch linked: lp:debian/sid/ntop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/138682
Title:
ntop permissions are not set right during install
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
** Changed in: ntop (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/138682
Title:
ntop permissions are not set right during install
--
ubuntu-bugs ma
OK. I can see that I need to be a bit more specific. What I just experienced on
Maverick is exactly what MarcRandolph wrote on 2008-11-08:
Installing ntop (sudo apt-get install ntop) on a machine (10.10 Maverick) where
ntop have never been installed before gives messages like
Warning: The home di
I just experienced this on Maverick 10.10 (after upgrades from previous
releases).
However when I did
sudo apt-get purge ntop
sudo apt-get install ntop
There was no problems. The purge command removed /var/lib/ntop. So the
install after that did not run into directory-exists problem.
--
You rec
on Karmic, this is sufficient to get ntop to start and log RRD network
data:
sudo apt-get install ntop
sudo install -d /var/lib/ntop
sudo install -o nobody -d /var/lib/ntop/interfaces
sudo install -o nobody -d /var/lib/ntop/rrd
sudo ntop
A little more detail on my blog:
http://johntellsall.blogsp
Related problem occuring in Hardy/8.04.1.
ntop not previously installed gives funny messages which appear to be the
result of incorrect ownership... /var/lib/ntop is owned by root rather than
ntop. Since it is recommended that users NOT run ntop as root, the directory
seems like it should be
The problem seems more complex than just the ownership of the
/var/lib/ntop directory.
When running the default /etc/init.d/ntop script, I get the following
error:
[EMAIL PROTECTED]:/var/lib/ntop# sudo /etc/init.d/ntop start
Starting network top daemon: Fri Apr 11 13:14:18 2008 NOTE: Interface m
I have a fresh gutsy install, and /var/lib/ntop is owned by ntop:root.
However, all files in that folder belongs to root:root. After chmod'ing,
the application runs and seems to be working fine.
--
ntop permissions are not set right during install
https://bugs.launchpad.net/bugs/138682
You receiv
Ok, the command did produce some output, see the attachment. I noticed
that it said it's running as the requested user nobody. Might that be
the cause?
** Attachment added: "ntop_output.txt"
http://launchpadlibrarian.net/11166581/ntop_output.txt
--
ntop permissions are not set right during in
I didn't use a snapshot, if that's what you mean. I upgraded through
fiesty. So no, I suppose not. Would that have made a difference? I
hadn't ever installed ntop before, so either way it would have had to
create those directories for the first time.
--
ntop permissions are not set right during i
Strange, on a gutsy fresh install, /var/lib/ntop is owned by ntop user
here. Is it a fresh install on your side?
** Changed in: ntop (Ubuntu)
Importance: Undecided => Low
Status: New => Triaged
--
ntop permissions are not set right during install
https://bugs.launchpad.net/bugs/138682
12 matches
Mail list logo
