reopen 438733 tag 438733 = confirmed severity 438733 important thanks Hrm, somehow I totally missed out on the "/usr mounted read-only" part, my bad; I will see what I can do about that...
Cheers, --Seb +On Sun, Sep 16, 2007 at 09:18:57PM -0300, Joaquín Martínez wrote: > Dear Sebastien, > > thanks to you. > > > Removing "confirmed" tag, and closing bug: lanmap is designed to > > run as root, since it needs raw access to the network interface, as > > illustrated below: > > But I am afraid that the problem that I was reporting was > related to /usr mounted read only, so even running as root > that temp file has not write access. > > I think that the /usr hierachy is not the best place to write > tmp data. I do not know if this is aganist the standard file > system practices... but it could be. > > Best regards. > > > > 2007/9/16, Debian Bug Tracking System <[EMAIL PROTECTED]>: > > This is an automatic notification regarding your Bug report > > which was filed against the lanmap package: > > > > #438733: lanmap: /usr/share/lanmap//tmp.lanmap on Read only /usr filesystem > > > > It has been closed by Sebastien Delafond <[EMAIL PROTECTED]>. > > > > Their explanation is attached below. If this explanation is > > unsatisfactory and you have not received a better one in a separate > > message then please contact Sebastien Delafond <[EMAIL PROTECTED]> by > > replying > > to this email. > > > > Debian bug tracking system administrator > > (administrator, Debian Bugs database) > > > > > > > > ---------- Mensagem encaminhada ---------- > > From: Sebastien Delafond <[EMAIL PROTECTED]> > > To: Joaquín Martínez <[EMAIL PROTECTED]>, [EMAIL PROTECTED] > > Date: Sun, 16 Sep 2007 18:16:48 +0200 > > Subject: Re: Bug#438733: lanmap: /usr/share/lanmap//tmp.lanmap on Read only > > /usr filesystem > > tag 438733 - confirmed > > thanks > > > > Removing "confirmed" tag, and closing bug: lanmap is designed to > > run as root, since it needs raw access to the network interface, as > > illustrated below: > > > > ~ # sudo chmod 777 /usr/share/lanmap > > ~ # lanmap -vvv -o /tmp > > verbosity level 3 > > using interfaces... > > reporting every 60 seconds... > > 8459 records loaded from /usr/share/lanmap//data/mac_vendor > > Couldn't find default interface: no suitable device found > > generating final report... > > ====== 0 Machines ======= > > cmd:twopi -Tpng -o /usr/share/lanmap//tmp.lanmap lanmap.dot && mv > > /usr/share/lanmap//tmp.lanmap /tmp/lanmap.png && rm lanmap.dot > > done. > > ~ # echo $? > > 1 > > ~ # > > > > Cheers, > > > > --Seb > > > > On Sun, Aug 19, 2007 at 10:17:17AM -0300, Joaquín Martínez wrote: > > > Package: lanmap > > > Version: 0.1+svn20060227-4 > > > Severity: grave > > > > > > > > > > > > -- System Information: > > > Debian Release: lenny/sid > > > APT prefers testing > > > APT policy: (500, 'testing') > > > Architecture: i386 (i686) > > > > > > Kernel: Linux 2.6.21-2-686 (SMP w/1 CPU core) > > > Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) > > > (ignored: LC_ALL set to en_IE.UTF-8) > > > Shell: /bin/sh linked to /bin/bash > > > > > > Versions of packages lanmap depends on: > > > ii graphviz 2.8-2.6 rich set of graph drawing > > > tools > > > ii libc6 2.6-2 GNU C Library: Shared > > > libraries > > > ii libpcap0.8 0.9.5-1 System interface for > > > user-level pa > > > > > > lanmap recommends no packages. > > > > > > -- debconf-show failed > > > > > > <above the emacs debian-bug command output> > > > > > > The exact and complete text of any error messages printed or logged. > > > (IPs and MAC info <REMOVED>): > > > > > > root # lanmap -vvv -o /tmp/ > > > /usr/share/lanmap//tmp.lanmap: Read-only file system > > > /usr/share/lanmap//tmp.lanmap: Read-only file system > > > verbosity level 3 > > > using devices... > > > reporting every 60 seconds... > > > 8459 records loaded from /usr/share/lanmap//data/mac_vendor > > > using device eth1... > > > opening eth1 in promiscuous mode... > > > device 'eth1' net: 0x0000A8C0, mask: 0x00FFFFFF > > > ====== 1 Machine ======= > > > Machine (134807496): > > > Roles: Bridge > > > Hostname: "" > > > Operating System: "?" > > > <REMOVED> > > > mac <REMOVED> <-> ip <REMOVED> > > > received signal 2, quitting... > > > generating final report... > > > ====== 2 Machines ======= > > > Machine (134807856): > > > Roles: Bridge > > > Hostname: "" > > > Operating System: "?" > > > <REMOVED> > > > Machine (134808968): > > > Roles: > > > Hostname: "" > > > Operating System: "?" > > > <REMOVED> > > > <REMOVED> > > > done. > > > > > > root # > > > > > > > > > A description of the incorrect behaviour: exactly what behaviour > > > you were expecting, and what you observed. > > > > > > Attempting to write on and read only filesystem /usr > > > and no image file is generated in /tmp/ > > > I was expecting that the temp data were under /var > > > > > > Suggested fix: 1) to use the /var hierachy to temp/lib/running data files > > > 2) to symlink the /usr file to an /var file on the installation scripts > > > > > > > > > I have added an CCO (I do not like to use his email on a public BTS) > > > to Ryan Flynn just to keep him informed. > > > > > > Thank you for your work and time. > > > > > > > > > Best regards > > > > > > > > > > > > -- > Gracias por la atención. > > Un saludo. > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
