Re: Re[2]: How to check where space is LOST
2011/9/12 Коньков Евгений kes-...@yandex.ru ** # fstat -f /var USER CMD PID FD MOUNT INUM MODE SZ|DV R/W clamav clamd 196823 /var 47113 -rw-r- 767747 w clamav smtp-gated 9428 wd /var 23569 drwxr-xr-x 512 r root snmpd 89483 /var 47171 -rw--- 282447082 w That is FD #3, how to find what file is that? find /var -inum 47171 -ls -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't log in as toor since package update
I don't really believe that toor user should be used like that - check the handbook for example. You better use normal user or the root itself. In 8.x the described is a normal behaviour. Regards, Ivailo Tanusheff Paul Keusemann pkeu...@visi.com Sent by: owner-freebsd-questi...@freebsd.org 09.09.2011 16:14 To freebsd-questions@freebsd.org cc Subject Can't log in as toor since package update I use the toor login on my FreeBSD systems to log in with the korn shell. Since August 22, When I try to log in as toor or even when I try to su - toor, I get logged in as root. For example: ushers# ssh -l toor woodstock Password: Last login: Fri Sep 9 06:30:23 2011 from 172.16.175.216 Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 8.2-RELEASE-p1 (WOODSTOCK) #1: Mon Jul 11 09:05:07 CDT 2011 woodstock# who am i root 0Sep 9 07:46 woodstock# su - toor woodstock# who am i root 0Sep 9 07:47 Unfortunately, I haven't tried to log in since a package update I did around August 22, so I didn't notice this problem until now. Does anybody have any idea what might be causing this? -- Paul Keusemann pkeu...@visi.com 4266 Joppa Court (952) 894-7805 Savage, MN 55378 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Disclaimer: The information contained in this message is intended solely for the use of the individual or entity to whom it is addressed and to others authorised to receive it. It may contain confidential or legally privileged information. It you are not the intended recipient you are hereby notified that any disclosure, copying, distribution, or taking any action based on the contents of this message is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this e-mail and then delete it from your system. ProCredit Bank is neither liable for the proper and complete transmission for the information contained in this message nor for any delay in its receipt. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't log in as toor since package update -- solved
On 09/09/11 07:52, Paul Keusemann wrote: I use the toor login on my FreeBSD systems to log in with the korn shell. Since August 22, When I try to log in as toor or even when I try to su - toor, I get logged in as root. For example: ushers# ssh -l toor woodstock Password: Last login: Fri Sep 9 06:30:23 2011 from 172.16.175.216 Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 8.2-RELEASE-p1 (WOODSTOCK) #1: Mon Jul 11 09:05:07 CDT 2011 woodstock# who am i root 0Sep 9 07:46 woodstock# su - toor woodstock# who am i root 0Sep 9 07:47 Unfortunately, I haven't tried to log in since a package update I did around August 22, so I didn't notice this problem until now. Does anybody have any idea what might be causing this? It turns out this was a bug introduced in version 272 of xterm which was one of the packages I updated. The maintainer was able to reproduce and fix the bug which will be in version 275 of xterm. -- Paul Keusemannpkeu...@visi.com 4266 Joppa Court (952) 894-7805 Savage, MN 55378 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re[2]: How to check where space is LOST
Zdravstvujte, Adam. Vy pisali 12 sentyabrya 2011 g., 3:32:06: 2011/9/11 Kon'kov Evgenij [1]kes-...@yandex.ru If I just #reboot system. I get that on /var is only 98M used. # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad1s1a496M239M217M52%/ devfs 1.0K1.0K 0B 100%/dev /dev/ad1s1e124M 40K114M 0%/tmp /dev/ad1s1f1.8G1.1G596M65%/usr /dev/ad1s1d989M 98M891M12%/var devfs 1.0K1.0K 0B 100%/var/named/dev How to obtain what take space on /var fstat -f /var -- Adam Vande More # fstat -f /var USER CMD PID FD MOUNT INUM MODE SZ|DV R/W root cron 20455 wd /var 47105 drwxr-x--- 512 r root cron 204553 /var 94235 -rw--- 5 w smmspsendmail 20432 wd /var 23564 drwxrwx---8192 r smmspsendmail 204324 /var 23567 -rw--- 51 w root sendmail 20418 wd /var 23561 drwxr-xr-x 512 r root sendmail 204185 /var 94226 -rw--- 80 w clamav clamd 196823 /var 47113 -rw-r- 767747 w clamav smtp-gated 9428 wd /var 23569 drwxr-xr-x 512 r root snmpd 89483 /var 47171 -rw--- 282447082 w root snmpd 89488 /var 47187 -rw-r- 728 r bind named 7738 root /var 70659 drwxr-xr-x 512 r bind named 7738 wd /var 70672 drwxr-xr-x 512 r bind named 7738 jail /var 70659 drwxr-xr-x 512 r root mpd537614 /var 94245 -rw-r--r-- 5 rw root syslogd 37423 /var 94231 -rw--- 4 w root syslogd 3742 13 /var 47122 -rw-r--r-- 182 w root syslogd 3742 14 /var 47131 -rw--- 99770 w root syslogd 3742 15 /var 47114 -rw--- 79173 w root syslogd 3742 16 /var 47136 -rw-r- 360039 w root syslogd 3742 17 /var 47134 -rw-r--r-- 56 w root syslogd 3742 18 /var 47194 -rw--- 56 w root syslogd 3742 19 /var 47127 -rw--- 90695 w root syslogd 3742 20 /var 47128 -rw--- 99531 w root syslogd 3742 21 /var 47157 -rw-r- 56 w root syslogd 3742 22 /var 47153 -rw--- 69165428 w root syslogd 3742 23 /var 47144 -rwxr-xr-x 10941641 w root devd36835 /var 94230 -rw--- 4 w That is FD #3, how to find what file is that? -- S uvazheniem, Kon'kov [2]mailto:kes-...@yandex.ru References 1. mailto:kes-...@yandex.ru 2. mailto:kes-...@yandex.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: KVM switch with FreeBSD-8.2
On 9/11/2011 at 2:28 PM Daniel Feenberg wrote: |The problem I have heard of relates to what happens if the machine boots |with the KVM switched to another machine? The KVM may need to pretend |there is a keyboard connected at that point. = I've used Avocent KVMs and this does not seem to be an issue with them. Currently I have a Avocent Switchview 100 PS/2 two-port sharing the console between FreeBSD 8.2 and OpenBSD 4.9 boxen. No issues regarding where the switch is pointing and which is booting. I do not use a GUI on either of those. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Mumble
On Sat, 10 Sep 2011 01:52:14 -0500, Mr. Darren darren...@yahoo.com wrote: I am trying to install Mumble on a headless FreeBSD server which has no need for X11. Why is this port trying to install X11? Seems like it shouldn't be needed. QT4. It's required for the server still. Sorry. There's a non-QT server but it's for the 1.1.x series, not the 1.2.x mumble version which is greatly improved. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: KVM switch with FreeBSD-8.2
On Sun, Sep 11, 2011 at 4:43 PM, Polytropon free...@edvax.de wrote: On Sun, 11 Sep 2011 15:10:48 -0600 (MDT), Warren Block wrote: On Sun, 11 Sep 2011, Daniel Feenberg wrote: If you are asking, Is there a FreeBSD command to cause the KVM switch to move to the next system? then the answer is I don't know and it would amaze me if there were. There's often a key sequence to advance to the next port or a specific port. That can _sometimes_ be a problem when the KVM switch doesn't properly detect this sequence - or maybe the user has already defined that sequence for some action in X, so X catches the sequence and acts properly. X catching the sequence won't stop the switch from reacting to it -- it's done in hardware in the switch. But of course X may do something undesirable if the switch passes the key combination through. The two most common ones are Ctrl, Alt, Shift (rapidly in sequence) followed by a port number, or Ctrl twice. The latter can be a little too easy to trigger accidentally. The USB switches generally emulate a generic USB keyboard and mouse, so drivers aren't a problem. Sometimes they work by simulating a USB disconnect from the machine they're switching to, though, so you need good keyboard and mouse hotplug support in the OS. Generally these switches don't react well to having anything but a keyboard in the keyboard port and a mouse in the mouse port. If you have a hub built into your keyboard the hub will be useless when you're using one of these switches. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: KVM switch with FreeBSD-8.2
On Mon, Sep 12, 2011 at 10:45 AM, David Brodbeck g...@gull.us wrote: The USB switches generally emulate a generic USB keyboard and mouse, so drivers aren't a problem. Sometimes they work by simulating a USB disconnect from the machine they're switching to, though, so you need good keyboard and mouse hotplug support in the OS. Err, clearly I meant simulating a USB disconnect from the machine they're switching FROM. :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Need an audio multicasting solution
Victor Sudakov v...@mpeks.tomsk.su, 2011-09-09 08:21 (+0200): I need a solution to read sound from a soundcard (/dev/dsp) and multicast it into the network, for the multicast audio stream to be played on FreeBSD, Linux and Windows workstations. Does the old LBL vat tool still work on modern system? http://ee.lbl.gov/vat/ I haven't used it for 15 years or so but it worked back then. Also, the Robust Audio Tool (rat) might still work. Seems to need work to get it running on FreeBSD according to their website but it used to work on FreeBSD. Again, it was over ten years ago I used this. It seems to live here nowadays: http://mediatools.cs.ucl.ac.uk/nets/mmedia/wiki/RatWiki#RobustAudioToolRAT Quotes: RAT require no special features for point-to-point communication, just a network connection and a soundcard. For multiparty conferencing RAT uses IP multicast and therefore all participants must reside on a multicast capable network. ... RAT is a cross platform tool which is now available for Linux and WinXP. In the past it was also maintained for use a variety of operating systems including: FreeBSD, HP-UX, IRIX, NetBSD, Solaris, SunOS, and Windows 95/NT. Users are welcome to test and contribute code for any of these other OSes. Please let us know or contribute to the wiki. -- http://hack.org/mc/ Use plain text e-mail, please. HTML messages silently dropped. OpenPGP welcome, 0xE4C92FA5. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Negative ping times with FreeBSD 8.1-RELEASE on older Celeron system
Here's a puzzler. I just put FreeBSD 8.1 up on an old (but good) 500 MHz Celeron with half a gig of RAM. Interfaces are classic xl (3Com) and dc (DEC tulip). Works quite nicely except for one quirk: ping times that ought to be positive (no more than 200 ms worst case) are coming out negative! Can't figure out what might be causing this. dmesg output is as follows: Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.1-RELEASE-p2 #5: Fri Apr 15 16:10:53 MST 2011 br...@washington.lariat.net:/usr/obj/usr/src/sys/WASHINGTON i386 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (501.14-MHz 686-class CPU) Origin = GenuineIntel Id = 0x665 Family = 6 Model = 6 Stepping = 5 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 536870912 (512 MB) avail memory = 515813376 (491 MB) acpi0: AMIINT AMIINT10 on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 atapci0: SiS 620 UDMA66 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at devic e 0.1 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] isab0: PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 pci0: unknown at device 1.1 (no driver attached) pci0: serial bus, USB at device 1.2 (no driver attached) pcib1: PCI-PCI bridge at device 2.0 on pci0 pci1: PCI bus on pcib1 vgapci0: VGA-compatible display port 0xbc00-0xbc7f mem 0xee80-0xeeff,0xef6f-0xef6f irq 11 at device 0.0 on pci1 xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xdc00-0xdc7f mem 0xefffaf80-0xefffafff irq 11 at devic e 8.0 on pci0 miibus0: MII bus on xl0 xlphy0: 3c905C 10/100 internal PHY PHY 24 on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:01:03:be:8b:c1 xl0: [ITHREAD] dc0: ADMtek AN985 10/100BaseTX port 0xd800-0xd8ff mem 0xefffa800-0xefffabff irq 12 at device 9.0 o n pci0 miibus1: MII bus on dc0 ukphy0: Generic IEEE 802.3u media interface PHY 1 on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:14:bf:5b:f5:ed dc0: [ITHREAD] xl1: 3Com 3c905B-TX Fast Etherlink XL port 0xd400-0xd47f mem 0xefffaf00-0xefffaf7f irq 9 at device 10.0 on pci0 miibus2: MII bus on xl1 xlphy1: 3Com internal media interface PHY 24 on miibus2 xlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl1: Ethernet address: 00:40:ca:97:13:7a xl1: [ITHREAD] acpi_button0: Power Button on acpi0 acpi_button0: enable wake failed atrtc0: AT realtime clock port 0x70-0x71 irq 8 on acpi0 orm0: ISA Option ROMs at iomem 0xc-0xc7fff,0xc8000-0xc87ff,0xc8800-0xd7fff pnpid ORM on is a0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] Timecounter TSC frequency 501141912 Hz quality 800 Timecounters tick every 1.000 msec ipfw2 initialized, divert loadable, nat enabled, rule-based forwarding enabled, default to accept, l ogging disabled load_dn_sched dn_sched PRIO loaded load_dn_sched dn_sched QFQ loaded load_dn_sched dn_sched RR loaded load_dn_sched dn_sched WF2Q+ loaded load_dn_sched dn_sched FIFO loaded ad0: 9787MB QUANTUM FIREBALLlct10 10 A03.0900 at ata0-master UDMA66 Trying to mount root from ufs:/dev/ad0s1a Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) xl0: promiscuous mode enabled xl0: promiscuous mode disabled dc0: TX underrun -- increasing TX threshold dc0: TX underrun -- increasing TX threshold Any hints here as to what's wrong? --Brett Glass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: KVM switch with FreeBSD-8.2
On Mon, 12 Sep 2011 10:45:59 -0700, David Brodbeck wrote: On Sun, Sep 11, 2011 at 4:43 PM, Polytropon free...@edvax.de wrote: On Sun, 11 Sep 2011 15:10:48 -0600 (MDT), Warren Block wrote: On Sun, 11 Sep 2011, Daniel Feenberg wrote: If you are asking, Is there a FreeBSD command to cause the KVM switch to move to the next system? then the answer is I don't know and it would amaze me if there were. There's often a key sequence to advance to the next port or a specific port. That can _sometimes_ be a problem when the KVM switch doesn't properly detect this sequence - or maybe the user has already defined that sequence for some action in X, so X catches the sequence and acts properly. X catching the sequence won't stop the switch from reacting to it -- it's done in hardware in the switch. But of course X may do something undesirable if the switch passes the key combination through. Yes, I thought of something like that _might_ happen, depending on the firmware of the KVM switch. You know, keys that are useful to users may be a first-class candidate for the manufacturer to say: Oh look, nobody uses *that* key, let's hardcode it as switching key! :-) The two most common ones are Ctrl, Alt, Shift (rapidly in sequence) followed by a port number, or Ctrl twice. The latter can be a little too easy to trigger accidentally. Fully agree, that's not very well thought... but maybe the product designers primarily orient at the Windows main target group that hardly uses the keyboard. :-) The USB switches generally emulate a generic USB keyboard and mouse, so drivers aren't a problem. Sometimes they work by simulating a USB disconnect from the machine they're switching to, though, so you need good keyboard and mouse hotplug support in the OS. FreeBSD's devd should handle that fine. Also the absense of a keyboard at system startup shouldn't matter. Generally these switches don't react well to having anything but a keyboard in the keyboard port and a mouse in the mouse port. If you have a hub built into your keyboard the hub will be useless when you're using one of these switches. Uh, that can be a problem when using professional desktop equipment, e. g. a Sun keyboard where you can connect the mouse directly to the keyboard (a feature known from the Apple ADB configurations of the 80's, if I remember correct- ly, but Sun also had this functionality in the pre-USB era; it's also a feature returning in Apple's modern USB products to attach the short-wired mouse to the keyboard's USB hub). I furthermore assume using the keyboard's hub for attaching other USB devices (memory sticks, MP3 players or cameras) to the keyboard's hub is a no-go then. Regarding the possible problem with monitors: As an example, the Nvidia documentation (HTML version located at /usr/local/share/doc/NVIDIA_GLX-1.0/html/) contains this interesting option: Option ConnectedMonitor string Allows you to override what the NVIDIA kernel module detects is connected to your graphics card. This may be useful, for example, if you use a KVM (keyboard, video, mouse) switch and you are switched away when X is started. In such a situation, the NVIDIA kernel module cannot detect which display devices are connected, and the NVIDIA X driver assumes you have a single CRT. Something similar _may_ be useful in case of too much malfunctioning autodetection magic. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re[4]: How to check where space is LOST
Hi, Adam # fstat -f /var USER CMD PID FD MOUNT INUM MODE SZ|DV R/W root snmpd 205453 /var 47141 -rw--- 37217152 w root snmpd 205458 /var 47159 -rw-r- 728 r root cron 20455 wd /var 47105 drwxr-x--- 512 r ... # find /var -inum 47141 -ls OutPut is empty (( 2011/9/12 Kon'kov Evgenij [1]kes-...@yandex.ru # fstat -f /var USER CMD PID FD MOUNT INUM MODE SZ|DV R/W clamav clamd 196823 /var 47113 -rw-r- 767747 w clamav smtp-gated 9428 wd /var 23569 drwxr-xr-x 512 r root snmpd 89483 /var 47171 -rw--- 282447082 w That is FD #3, how to find what file is that? find /var -inum 47171 -ls -- Adam Vande More -- S uvazheniem, Kon'kov [2]mailto:kes-...@yandex.ru References 1. mailto:kes-...@yandex.ru 2. mailto:kes-...@yandex.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
BUG: snmpd or How to check where space is LOST
Здравствуйте, Robert. Вы писали 12 сентября 2011 г., 10:28:22: From kes-...@yandex.ru Mon Sep 12 00:51:16 2011 Date: Mon, 12 Sep 2011 08:51:27 +0300 From: =?windows-1251?B?yu7t/Oru4iDF4uPl7ejp?= kes-...@yandex.ru To: Robert Bonomi bon...@mail.r-bonomi.com Subject: Re[2]: How to check where space is LOST Caoaanoaoeoa, Robert. u ienaee 12 naioyaoy 2011 a., 4:33:25: From owner-freebsd-questi...@freebsd.org Sun Sep 11 17:23:57 2011 Date: Mon, 12 Sep 2011 01:23:32 +0300 From: =?windows-1251?B?yu7t/Oru4iDF4uPl7ejp?= kes-...@yandex.ru To: freebsd-questions@freebsd.org Subject: How to check where space is LOST Hi. I notice that some times /var is overfull # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad1s1d989M349M561M38%/var # cd /var/ # du -h -d 1 98M. If I just #reboot system. I get that on /var is only 98M used. # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad1s1d989M 98M891M12%/var How to obtain what take space on /var RB Probably, you *don't*. grin RB df _is_ telling the truth. RB 'du' is, arguably, 'telling lies'. RB The difference concerns files that have been deleted (rm) _after_ RB they have been opened, and not yet closed. The file handle/descriptor RB that has the file open silll has access to all the data in the file. RB but *NOTHING*ELSE* -- inlcuding 'du' -- can access that file, so the RB space occupied by that deletedd file is not counted. RB Note: this *IS* a FAQ. thank you very much. fstat -f /var tell me that process snmpd with file descriptor 3 take spece: RB It's not unreasonable that snmpd (the 'simple network management protocol' RB daemon) needs a *lot* of private storage. RB In short, don't worry about it. Ok, How you can explain this: # df -h /dev/ad1s1d989M138M772M15%/var # fstat -f /var USER CMD PID FD MOUNT INUM MODE SZ|DV R/W root snmpd 205453 /var 47141 -rw--- 37217152 w root snmpd 205458 /var 47159 -rw-r- 728 r snmpd has 35MB of space # find /var -inum 47141 -ls output is empty (( # /usr/local/etc/rc.d/snmpd restart Stopping snmpd. Starting snmpd. # df -h /dev/ad1s1d989M102M808M11%/var # fstat -f /var/ USER CMD PID FD MOUNT INUM MODE SZ|DV R/W root snmpd 407663 /var 47171 -rw--- 23311 w root snmpd 407668 /var 47159 -rw-r- 728 r after 3-4 weeks and snmpd overfull /var filesystem Test on other system: # df -h /dev/ad0s1d6.7G2.1G4.1G34%/var # fstat -f /var | grep snmp root snmpd 71403 -588866 -rw-r--r-- 947424261 w root snmpd 71408 /var 588842 -rw-r- 728 r # /usr/local/etc/rc.d/snmpd restart Stopping snmpd. Waiting for PIDS: 7140. Starting snmpd. # fstat -f /var | grep snmp root snmpd 233763 /var 588894 -rw-r--r-- 132 w root snmpd 233768 /var 588872 -rw-r- 728 r # df -h /dev/ad0s1d6.7G1.2G 5G19%/var It seems that that is the BUG of snmpd # snmpd -v NET-SNMP version: 5.5 Web: http://www.net-snmp.org/ Email: net-snmp-cod...@lists.sourceforge.net # uname -a FreeBSD flux 9.0-CURRENT FreeBSD 9.0-CURRENT #4: Fri Jun 10 01:30:12 UTC 2011 adm@:/usr/obj/usr/src/sys/PAE_KES i386 -- С уважением, Коньков mailto:kes-...@yandex.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Re[4]: How to check where space is LOST
2011/9/12 Коньков Евгений kes-...@yandex.ru # fstat -f /var USER CMD PID FD MOUNT INUM MODE SZ|DV R/W root snmpd 205453 /var 47141 -rw--- 37217152 w root snmpd 205458 /var 47159 -rw-r- 728 r root cron 20455 wd /var 47105 drwxr-x--- 512 r ... # find /var -inum 47141 -ls You find the inode number with fstat then use find to translate it to a filename. It works fine here, if it doesn't work for you perhaps you have a user error or there is some other sort of bug. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Re[4]: How to check where space is LOST
2011/9/12 Adam Vande More amvandem...@gmail.com 2011/9/12 Коньков Евгений kes-...@yandex.ru # fstat -f /var USER CMD PID FD MOUNT INUM MODE SZ|DV R/W root snmpd 205453 /var 47141 -rw--- 37217152 w root snmpd 205458 /var 47159 -rw-r- 728 r root cron 20455 wd /var 47105 drwxr-x--- 512 r ... # find /var -inum 47141 -ls You find the inode number with fstat(1) then use find(1) to translate it to a filename. It works fine here, if it doesn't work for you perhaps you have a user error or there is some other sort of bug. One other thing, it's possible the inode is gone by the time you have run find(1) so be sure you are working with current fstat(1) output. May be easier to script the transform if this is something you are doing regularly. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Crash when copying large files
Hello! I'm trying to move a filesystem to a new larger RAID volume. The old filesystem was using gjournal, and I have also created the new filesystem with gjournal. The FS in question holds the DocumentRoot of our web server, and in its depths, a couple of fairly large (several gigabytes) files are lurking. I've mounted the new FS under /mnt and use tar to transfer the files: cd /mnt tar -c -v -f - -C /docroot . | tar xf - It seems that these large files cause a problem. Sometimes when the process reaches one of these files, the machine reboots. It doesn't create a crashdump in /var/crash, which may be because the system has less swap (2 GB) than RAM (8 GB). Fortunately the machine comes back up OK, except that the target FS (/mnt) is corrupt and needs to be fsck'd. I've tried to re-run the process three times now, and caused the machine to crash as it reaches one or another large file. Any ideas what I should do to avoid the crash? The OS version is 7.3 (amd64). -- Toomas Aas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Crash when copying large files
On Tue, 13 Sep 2011 00:14:45 +0300, Toomas Aas wrote: Hello! I'm trying to move a filesystem to a new larger RAID volume. The old filesystem was using gjournal, and I have also created the new filesystem with gjournal. The FS in question holds the DocumentRoot of our web server, and in its depths, a couple of fairly large (several gigabytes) files are lurking. I've mounted the new FS under /mnt and use tar to transfer the files: cd /mnt tar -c -v -f - -C /docroot . | tar xf - It seems that these large files cause a problem. Sometimes when the process reaches one of these files, the machine reboots. It doesn't create a crashdump in /var/crash, which may be because the system has less swap (2 GB) than RAM (8 GB). Fortunately the machine comes back up OK, except that the target FS (/mnt) is corrupt and needs to be fsck'd. I've tried to re-run the process three times now, and caused the machine to crash as it reaches one or another large file. Any ideas what I should do to avoid the crash? The par program operates on a per-file basis. In case that causes a problem, try to leave this route and use the old- fashioned tools dump and restore. Make sure the file system isn't mounted, then use: # cd /your/target/directory # dump -0 -f - /dev/sourcedev | restore -r -f - wheree sourcedev refers to the device you've initially mounted /mnt from. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Crash when copying large files
Hi-- On Sep 12, 2011, at 2:14 PM, Toomas Aas wrote: I've mounted the new FS under /mnt and use tar to transfer the files: cd /mnt tar -c -v -f - -C /docroot . | tar xf - You probably wanted -p flag on the extract side. The manpage recommends one of the following constructs: To move file hierarchies, invoke tar as tar -cf - -C srcdir . | tar -xpf - -C destdir or more traditionally cd srcdir ; tar -cf - . | (cd destdir ; tar -xpf -) However, this isn't going to resolve the system panic'ing. Certainly, that's not a reasonable behavior... :-) It seems that these large files cause a problem. Sometimes when the process reaches one of these files, the machine reboots. It doesn't create a crashdump in /var/crash, which may be because the system has less swap (2 GB) than RAM (8 GB). Fortunately the machine comes back up OK, except that the target FS (/mnt) is corrupt and needs to be fsck'd. I've tried to re-run the process three times now, and caused the machine to crash as it reaches one or another large file. Any ideas what I should do to avoid the crash? Right, a machine with 8GB of RAM isn't going to be able to dump to a 2GB swap area. (Although, I seem to recall some folks working on compressed crash dumps, but I don't know what state that is in.) But you can set hw.physmem in loader.conf to limit the RAM being used to 2GB so you can generate a crash dump if you wanted to debug it further. How big are your multi-GB files, anyway? If you want a workaround to avoid the crash, consider using either rsync or dump/restore to copy the filesystem, rather than using tar. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Negative ping times with FreeBSD 8.1-RELEASE on older Celeron system
More information regarding the odd behavior I'm seeing. Turns out that packets do not even need to leave the machine for it to report large negative ping times, on the order of more than half a second. (See below.) Clearly something is odd about timekeeping in this system (SiS motherboard chipset, PII-generation Celeron but still effectively a 686) which was not a problem when it was running FreeBSD 4.11-RELEASE (as it was before). What's more, it appears that the negative ping times being shown for pings of localhost are off by about -687 ms, consistently. Any ideas? I am wondering if perhaps some recent change to the kernel assumed that one would always have a faster CPU than the old Celeron this machine is running, and that there is a race condition or an error in the kernel code. --Brett Glass # ping localhost PING localhost (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=-0.148 ms 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=-0.151 ms 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=-686.111 ms 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=-0.180 ms 64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.110 ms 64 bytes from 127.0.0.1: icmp_seq=5 ttl=64 time=686.351 ms 64 bytes from 127.0.0.1: icmp_seq=6 ttl=64 time=-686.376 ms 64 bytes from 127.0.0.1: icmp_seq=7 ttl=64 time=0.121 ms 64 bytes from 127.0.0.1: icmp_seq=8 ttl=64 time=-686.402 ms 64 bytes from 127.0.0.1: icmp_seq=9 ttl=64 time=-686.105 ms 64 bytes from 127.0.0.1: icmp_seq=10 ttl=64 time=686.623 ms 64 bytes from 127.0.0.1: icmp_seq=11 ttl=64 time=0.107 ms 64 bytes from 127.0.0.1: icmp_seq=12 ttl=64 time=0.119 ms 64 bytes from 127.0.0.1: icmp_seq=13 ttl=64 time=0.418 ms 64 bytes from 127.0.0.1: icmp_seq=14 ttl=64 time=0.401 ms 64 bytes from 127.0.0.1: icmp_seq=15 ttl=64 time=-0.169 ms 64 bytes from 127.0.0.1: icmp_seq=16 ttl=64 time=0.113 ms 64 bytes from 127.0.0.1: icmp_seq=17 ttl=64 time=0.401 ms 64 bytes from 127.0.0.1: icmp_seq=18 ttl=64 time=-686.117 ms 64 bytes from 127.0.0.1: icmp_seq=19 ttl=64 time=0.115 ms 64 bytes from 127.0.0.1: icmp_seq=20 ttl=64 time=0.111 ms ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
libreoffice-systray
First thank you for the Libreoffice 3.4.3_1. I built it with systray support, enable in the options and it doesn't work on my FreeBSD 8.2, KDE 4.6.5. Thanks. Mitja http://jpgmag.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Negative ping times with FreeBSD 8.1-RELEASE on older Celeron system
On Sep 12, 2011, at 4:50 PM, Brett Glass wrote: What's more, it appears that the negative ping times being shown for pings of localhost are off by about -687 ms, consistently. Any ideas? Your system's timekeeping appears to be busted. Are you running ntpd with tinker step 0.0 or some home-grown mechanism which might be forcibly stepping the clock rather than skewing it, by any chance? Anyway, the output of: sysctl -a kern.timecounter ...is likely to be informative. Try switching to another clock type, especially ACPI-safe if it hasn't been chosen by default. Your CPU is probably too old to have a power-state invariant TSC, but if you disable SpeedStep, powerd and similar which might change the processor frequency, TSC might work OK also. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Crash when copying large files
ftp the large files, then tar? I like the rsync idea too. - Original Message - From: Chuck Swiger [mailto:cswi...@mac.com] Sent: Monday, September 12, 2011 06:42 PM To: Toomas Aas toomas@raad.tartu.ee Cc: questi...@freebsd.org questi...@freebsd.org Subject: Re: Crash when copying large files Hi-- On Sep 12, 2011, at 2:14 PM, Toomas Aas wrote: I've mounted the new FS under /mnt and use tar to transfer the files: cd /mnt tar -c -v -f - -C /docroot . | tar xf - You probably wanted -p flag on the extract side. The manpage recommends one of the following constructs: To move file hierarchies, invoke tar as tar -cf - -C srcdir . | tar -xpf - -C destdir or more traditionally cd srcdir ; tar -cf - . | (cd destdir ; tar -xpf -) However, this isn't going to resolve the system panic'ing. Certainly, that's not a reasonable behavior... :-) It seems that these large files cause a problem. Sometimes when the process reaches one of these files, the machine reboots. It doesn't create a crashdump in /var/crash, which may be because the system has less swap (2 GB) than RAM (8 GB). Fortunately the machine comes back up OK, except that the target FS (/mnt) is corrupt and needs to be fsck'd. I've tried to re-run the process three times now, and caused the machine to crash as it reaches one or another large file. Any ideas what I should do to avoid the crash? Right, a machine with 8GB of RAM isn't going to be able to dump to a 2GB swap area. (Although, I seem to recall some folks working on compressed crash dumps, but I don't know what state that is in.) But you can set hw.physmem in loader.conf to limit the RAM being used to 2GB so you can generate a crash dump if you wanted to debug it further. How big are your multi-GB files, anyway? If you want a workaround to avoid the crash, consider using either rsync or dump/restore to copy the filesystem, rather than using tar. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org font size=1 div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in' /div This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. /font ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Negative ping times with FreeBSD 8.1-RELEASE on older Celeron system
I just put FreeBSD 8.1 up on an old (but good) 500 MHz Celeron with half a gig of RAM. Interfaces are classic xl (3Com) and dc (DEC tulip). Works quite nicely except for one quirk: ping times that ought to be positive (no more than 200 ms worst case) are coming out negative! Can't figure out what might be causing this. dmesg output is as follows: If you are just upgrading now, why not use 9 BETA? I think that your older machine will be much happier -- the new timer code in 9 has a bunch of bugfixes, allows for a wider choice of alternative timers, in case some are broken, and places lighter loads on the system, by allowing some (formerly periodic) timer use to be deferred. And then there is the host of other improvements... b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ssh with bridged ap
I have set up wireless AP with a static IP and bridged it to my internal wired network on RE0. I can successfully connect with WPA to the wireless network and browse other computers on the wired net fine, I can log into the freebsd machine using ssh no problem as long as if I connect via the wireless network. If I try and log into the freebsd machine using the wired network I get a log in prompt for username Then I get the password prompt but after typing in my password it always says login incorrect, it don't do this if I am on the wireless net. Maybe something in the sshd config about bridged connections? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Negative ping times with FreeBSD 8.1-RELEASE on older Celeron system
At 06:15 PM 9/12/2011, Chuck Swiger wrote: Your system's timekeeping appears to be busted. Are you running ntpd with tinker step 0.0 or some home-grown mechanism which might be forcibly stepping the clock rather than skewing it, by any chance? Nothing like that. Anyway, the output of: sysctl -a kern.timecounter ...is likely to be informative. Here it is: kern.timecounter.tick: 1 kern.timecounter.choice: TSC(800) ACPI-safe(850) i8254(0) dummy(-100) kern.timecounter.hardware: ACPI-safe kern.timecounter.stepwarnings: 0 kern.timecounter.tc.i8254.mask: 4294967295 kern.timecounter.tc.i8254.counter: 5754 kern.timecounter.tc.i8254.frequency: 1193182 kern.timecounter.tc.i8254.quality: 0 kern.timecounter.tc.ACPI-safe.mask: 16777215 kern.timecounter.tc.ACPI-safe.counter: 7967112 kern.timecounter.tc.ACPI-safe.frequency: 3579545 kern.timecounter.tc.ACPI-safe.quality: 850 kern.timecounter.tc.TSC.mask: 4294967295 kern.timecounter.tc.TSC.counter: 4058536290 kern.timecounter.tc.TSC.frequency: 501141177 kern.timecounter.tc.TSC.quality: 800 kern.timecounter.invariant_tsc: 0 This is very instructive. I didn't know that FreeBSD used the Pentium internal timestamp counter for anything but profiling. I am noticing here that the mask (which I assume is the maximum value just before a rollover) for the ACPI-safe timer is very small. Maybe it's rolling over very frequently and/or the system is missing some of the rollovers. This would cause it to calculate negative times, of course. Try switching to another clock type, especially ACPI-safe if it hasn't been chosen by default. No docs on how to do this. Is this done by, for example, setting kern.timecounter.hardware=TSC in loader.conf? Your CPU is probably too old to have a power-state invariant TSC, but if you disable SpeedStep, powerd and similar which might change the processor frequency, TSC might work OK also. I've already turned off all power saving mechanisms listed in the BIOs setup, including clock speed modulation. So, the TSC ought to be pretty stable. At least it's worth a shot. --Brett Glass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Negative ping times with FreeBSD 8.1-RELEASE on older Celeron system
At 06:54 PM 9/12/2011, b. f. wrote: If you are just upgrading now, why not use 9 BETA? Production machine. Also, whenever we create a new production box, we normally pick the release (not beta; we need to be able to do binary upgrades and this is only supported from one release to another) with the EOL that's the farthest out. We'll retire the hardware before we will run non-release code on a production box. --Brett Glass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
how to make devfs show fdisk updates?
Dear all, I have recently been using fdisk(8) to activate additional partitions, but have been unable to cause the device nodes corresponding to the new partition to appear in /dev other than by rebooting. (This is on the device which contains the root filesystem, so kern.geom.debugflags=16 is necessary to perform the fdisk.) Please advise on how to effect the creation of the device node(s) in a non-disruptive fashion. Thanks, Ben Kaduk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to make devfs show fdisk updates?
On Tue, 13 Sep 2011 00:32:27 -0400 (EDT), Benjamin Kaduk wrote: Dear all, I have recently been using fdisk(8) to activate additional partitions, but have been unable to cause the device nodes corresponding to the new partition to appear in /dev other than by rebooting. (This is on the device which contains the root filesystem, so kern.geom.debugflags=16 is necessary to perform the fdisk.) Please advise on how to effect the creation of the device node(s) in a non-disruptive fashion. I think it's still common practice to taste the device file in order to make new partitions show up: # true /dev/da0 In this example, I assume that da0 is the _disk_ in question where you've added partitions. Now the proper device files (e. g. /dev/da0a, /dev/da0d, /dev/da0e, /dev/da0f... resp. /dev/da0s1a, /dev/da0s1d, /dev/da0s1e, /dev/da0s1f...) should appear in the device file system. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to make devfs show fdisk updates?
On Mon, Sep 12, 2011 at 11:32 PM, Benjamin Kaduk ka...@mit.edu wrote: Dear all, I have recently been using fdisk(8) to activate additional partitions, but have been unable to cause the device nodes corresponding to the new partition to appear in /dev other than by rebooting. (This is on the device which contains the root filesystem, so kern.geom.debugflags=16 is necessary to perform the fdisk.) Please advise on how to effect the creation of the device node(s) in a non-disruptive fashion. You can force a GEOM retaste by issuing a true /dev/devname. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Negative ping times with FreeBSD 8.1-RELEASE on older Celeron system
On Mon, Sep 12, 2011 at 10:30 PM, Brett Glass br...@lariat.net wrote: At 06:15 PM 9/12/2011, Chuck Swiger wrote: sysctl -a kern.timecounter No docs on how to do this. Is this done by, for example, setting kern.timecounter.hardware=TSC in loader.conf? it's a runtime tunable so /etc/sysctl.conf and the sysctl -a kern.timecounter doesn't need a -a -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
