Re: Critical Bug in 6.1 (nfs server bad performance)
Kris Kennaway <[EMAIL PROTECTED]> writes: > On Fri, Jun 02, 2006 at 03:17:46PM +0200, Marko Lerota wrote: >> After some testing I saw that nfs server with 6.1 release or stable >> have problems with CPU performance. >> >> I had 2 servers. One 5.4 and one 6.1. The servers are identical in >> configuration and only have nfs servers running. >> If you try to copy something to 6.1, CPU gets abnormal and load averages >> gets to 2,5 to 6 or more and thus kill the server. On 5.4 it's OK. Load >> averages is not over 0.50 ever. > > Please review the archives for the patch that is being reviewed. > > Kris Sorry, now I saw the post from Tue May 23. I also have the "options QUOTA" in kernel config. Why it's not in the errata html page? http://www.freebsd.org/releases/6.1R/errata.html -- One cannot sell the earth upon which the people walk Tacunka Witco ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Critical Bug in 6.1 (nfs server bad performance)
On Tue, Jun 06, 2006 at 09:24:15AM +0200, Marko Lerota wrote: > Kris Kennaway <[EMAIL PROTECTED]> writes: > > > On Fri, Jun 02, 2006 at 03:17:46PM +0200, Marko Lerota wrote: > >> After some testing I saw that nfs server with 6.1 release or stable > >> have problems with CPU performance. > >> > >> I had 2 servers. One 5.4 and one 6.1. The servers are identical in > >> configuration and only have nfs servers running. > >> If you try to copy something to 6.1, CPU gets abnormal and load averages > >> gets to 2,5 to 6 or more and thus kill the server. On 5.4 it's OK. Load > >> averages is not over 0.50 ever. > > > > Please review the archives for the patch that is being reviewed. > > > > Kris > > Sorry, now I saw the post from Tue May 23. I also have the "options QUOTA" > in kernel config. Why it's not in the errata html page? > > http://www.freebsd.org/releases/6.1R/errata.html Because the problem was still being reviewed and worked on. It has now been committed to CURRENT and will be merged shortly. Kris pgpjEqzWMvao4.pgp Description: PGP signature
Re: (some?) startup scripts being run twice..?
Make sure that you've run mergemaster and that everything (especially rc and rc.subr) is up to date. If that doesn't fix it, add rc_debug and rc_info to your /etc/rc.conf, and reboot. You probably also want to turn on console logging in /etc/syslogd.conf as well. hth, Doug ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
laptop multihoming [was: [OT] resolv.conf and dhclient]
On Mon, Jun 05, 2006 at 01:36:15PM -0700, Kevin Oberman wrote: > > I use Tobias Roth's profile.sh which is available from > https://secure.socket.ch/projects/profile/. It is less than perfect, but > works very well for me. It allows totally different user environments > depending on your network connection. > > It works by union mounting a different copy of /etc depending on what is > probed on the network. I have profiles for home (wireless), work (1 > location wired and 1 wired + wireless), and general random connections. > > Since the entire rc.conf as well as all other files in /etc may be > connection specific, you can do almost anything you want to vary the > config. Please allow me to make a remark about the current state of profile.sh. It currently works for me, and others. However, its architecture is based on the outdated assumption that location changes are only triggered at startup (startup in a new environment) or at resume (suspend and then resume somewhere else). Now, we are currently moving to a much more dynamic behaviour, where location changes can happen at any time. The new dhcp client as well as wpa supplicant are steps towards that direction. Profile.sh, though, is not suited for this. A better solution has to be found, that retains as much of the flexibility of profile.sh as possible. I am not yet actively working on this, and I don't know when I will have the time to start. But the topic of 'laptop multihoming' or whatever you want to call it is still important, I think. Thanks, Tobias ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dual Opteron system will not run SMP
> We (Intel networking group) have seen issues with SMP and amd64 > as well, although I dont know that its fully characterized (what works > and what doesnt) yet. When I tried mine under amd64 it seemed to behave slightly better oddly enough - it would at least boot up the SMP kernel without ACPI, though it would not recognise the second processor. The other difference when I was doing that test was that I was using an IDE drive though. I suppose I really need to put amd64 onto a normal disc drive and try booting that to narrow down which change made the difference there. > If just non-ACPI isnt sufficient, the other thing SAFE does is turn > off disk DMA. I have an as-yet unreleased system that has this > same type of issue, and the problem is that two PCI device ID's > are not recognized, so maybe that will be your problem. Interesting - I didn't realise you could do that with SCSI controllers. I had been wondering what 'safe' does differently, and whether I could fill up loader.conf with approrpiate values to emulate what 'safe' does and then start commenting them out one at a time. I'll do some more experiments and report back. I don't particularly mind if it doesn't work in the end (I'll just sell the pair of Opterons on ebay and buy a single faster one), but it's always good to try and track down a bug, so thanks for taking an interest. -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FTP - Large file transfers (6.1)
I am having repeated FTP failures while transferring a 4G file across a LAN. Swapped out the switch, cables, and NIC's so don't believe hardware is involved. Have tried the default FTP server as well as vsftp and pure-ftp with the same results. NICs tested are em, sk, and rl. How to duplicate failure: Take two 6.1 machines with a 100M lan or x-talk cable and try to FTP a DVD image. The transfer fails around 90% of the time with "450 Error during write to data connection" We have a similar problem when using samba. The failure is not as consistent but always occurs under heavy load. Here is the error: [2006/06/04 22:20:02, 0] lib/util_sock.c:write_data(557) write_data: write failure in writing to client 192.168.163.41. Error Host is down It appears, that the network connection on the server is being reset, but why? And where or how do I find more information? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FTP - Large file transfers (6.1)
On Tue, June 6, 2006 2:51 pm, David Samms wrote: > I am having repeated FTP failures while transferring a 4G file across a > LAN. Swapped out the switch, cables, and NIC's so don't believe hardware > is involved. Have tried the default FTP server as well as vsftp and > pure-ftp with the same results. NICs tested are em, sk, and rl. > > How to duplicate failure: Take two 6.1 machines with a 100M lan or > x-talk cable and try to FTP a DVD image. The transfer fails around 90% > of the time with > "450 Error during write to data connection" > > We have a similar problem when using samba. The failure is not as > consistent but always occurs under heavy load. Here is the error: > > [2006/06/04 22:20:02, 0] lib/util_sock.c:write_data(557) > write_data: write failure in writing to client 192.168.163.41. Error > Host is down > > It appears, that the network connection on the server is being reset, > but why? And where or how do I find more information? > Can you look here: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=110247+0+archive/2006/freebsd-net/20060205.freebsd-net The attached patch solved my problem. A temporary workaround was to use ProFTPD. -- WWell by Iassen Anadoliev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [OT] resolv.conf and dhclient
Damian Gerow <[EMAIL PROTECTED]> writes: > Thus spake Lowell Gilbert ([EMAIL PROTECTED]) [05/06/06 10:32]: > : > I've often wondered why dhclient.conf doesn't have an 'ignore' directive. > : > There's a 'require' in there; it doesn't seem like much of a stretch to > : > 'ignore' something. > : > : Why not just write a simple script for one of the hooks that > : dhclient-script(8) supports? > > I'd looked at this before (a few months back), and deemed it insufficient > for the job. However, upon your re-suggestion, I can't see why it /won't/ > work. It should also be able to figure out which wired LAN the machine is > connected to, and assign the appropriate DNS servers. So this /may/ > actually address my problem. (Goodness knows why I originally dismissed > it.) > > However, this ignores my original question: why is there no 'ignore' > directive in dhclient.conf? I don't think it does really beg the question: the existence of other options reduces the impetus for someone to write it and get it accepted in to the codebase. And hidden in there is the direct answer to your question: the feature doesn't exist because no one has written it. > It seems like a potentially incredibly useful > thing, and I run across posts from people who could greatly benefit from > this every couple of months. Perhaps, but most of the time "supersede" (or "prepend" or "append") will solve their problems fine. At least, that's my experience from watching this list. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[repost] Fresh install of 6.1/amd64 - Xorg driver problem with Nvidia 7600 GS (stock nv driver)
Hi all, Apologies for the repost (and slightly corrected) mail from freebsd-x11 - I recently built a new box, with A8N32-SLI Deluxe mobo, PCI-E geforce 7600 GS CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ (2210.07-MHz K8-class CPU) avail memory = 4000612352 (3815 MB) .. and built to 6.1-STABLE (including options SMP). The default Xorg which is installed at install time is broken on my machine. A 'xorgcfg', or testing the xorg.conf.new spews the following error, then sigabrt's. "Fatal server error: Caught signal 8. Server aborting" I have also removed the package Xorg, tried the one built from ports, but same error. Also, I tried xorg-server-snap, but same problem. Here's a backtrace from the core via gdb. #0 0x000800ca6c9c in kill () from /lib/libc.so.6 #1 0x000800ca5b2d in abort () from /lib/libc.so.6 #2 0x0042cb05 in ddxGiveUp () #3 0x004a6df3 in AbortServer () #4 0x004a6f41 in FatalError () #5 0x004442d1 in xf86SigHandler () #6 #7 0x000801f825c8 in nvGetClocks () from /usr/X11R6/lib/modules/drivers/nv_drv.so #8 0x000801f83588 in NVCalcStateExt () from /usr/X11R6/lib/modules/drivers/nv_drv.so #9 0x000801f7d6ba in NVDACInit () from /usr/X11R6/lib/modules/drivers/nv_drv.so #10 0x000801f7c905 in NVModeInit () from /usr/X11R6/lib/modules/drivers/nv_drv.so #11 0x000801f7ceb4 in NVScreenInit () from /usr/X11R6/lib/modules/drivers/nv_drv.so #12 0x0048e14f in AddScreen () #13 0x0042e038 in InitOutput () #14 0x0048dae5 in main () .. and here is what is reported from pciconf -lv none11 at pci3:0:0:class=0x03 card=0x22211682 chip=0x039210de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' class= display subclass = VGA the "none11" part fills me with suspicion - is there a specific kernel config option to use with PCI-E devices? Apart from this, everything else works just fine (apart from nve0 instability, but i don't use the i/f...). The BusID's are correct in the xorg.conf (as per pciconf output). This is most likely an unsupported chipset (although nv(4) does mention the GeForce 7XXX series, albeit the G70, but I believe my card is that very one). I may try and graft in the nv driver from Xorg R7.1 if at all there's been any progress with it since 6.9.0. I can use X with the vesa driver, but value my eyesight and therefore will endeavour to get this cracked with nv. I'd appreciate any pointers in the right direction Thanks for your time. Dan. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fresh install of 6.1/amd64 - Xorg driver problem with Nvidia 7600 GS (stock nv driver)
Sorry to reply to my own post, but in my endeavours to seek out more information about what's occuring, I notice that nv_driver.c's struct SymTabRec NvKnownChipsets[], my card is not listed. also, nv(4) w/ Xorg 6.9.0 mentions that the GeForce 7XXX (G70) is supported, but XFree86 4.6.0's nv(4) mentions GeForce 7XXX (G70,G71,G72,G73), and the card I have is in fact a G72. I will give XFree a try tonight. Thanks for your time Dan. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ath problems when in if_bridge mode
Hi I find some problems when running ath cards in if_bridge mode. I have continuous UP/DOWN events on the uplink card. The connection is really interrupted for a second or so which results in dns lookup errors downloads are going through, only the download speed is not stable please look close, the problem is not on the hostap card the problem is not hw related, I can switch both cards and the problem stays on the uplink card I can take the bridge off and stay connected without UP/DOWN events (same machine/same HW) the other wierd thing is that when I compile ath_rate_sample the both cards are working basicly but no traffic goes through the bridge, when I compile ath_rate_onoe the traffic goes through, when I take the bridge off and use the machine as router the traffic goes through. the above does not change wether I put the uplink card in STP or not I tried latest releng_6 i386 and amd64 and it is the same result If you think I should check something please tell me João Jun 6 11:43:17 ap-h kernel: ath0: link state changed to DOWN Jun 6 11:43:17 ap-h kernel: ath0: link state changed to UP Jun 6 11:43:23 ap-h kernel: ath0: link state changed to DOWN Jun 6 11:43:23 ap-h kernel: ath0: link state changed to UP Jun 6 11:43:30 ap-h kernel: ath0: link state changed to DOWN Jun 6 11:43:30 ap-h kernel: ath0: link state changed to UP Jun 6 11:43:45 ap-h kernel: ath0: link state changed to DOWN Jun 6 11:43:45 ap-h kernel: ath0: link state changed to UP ifconfig ath0: flags=8943 mtu 1500 inet 200.152.80.36 netmask 0xfff8 broadcast 200.152.80.39 ether 00:13:46:8b:f2:52 media: IEEE 802.11 Wireless Ethernet DS/11Mbps (DS/11Mbps) status: associated ssid LUCENET-CS channel 1 bssid 00:02:6f:3a:98:b3 authmode OPEN privacy ON deftxkey 1 wepkey 1:40-bit wepkey 2:40-bit wepkey 3:40-bit wepkey 4:40-bit txpowmax 36 protmode CTS burst bintval 100 ath1: flags=8943 mtu 1500 inet 200.152.88.33 netmask 0xfff8 broadcast 200.152.88.39 ether 00:11:95:c2:2a:80 media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g status: associated ssid casa channel 11 bssid 00:11:95:c2:2a:80 authmode OPEN privacy OFF txpowmax 36 protmode CTS burst ssid HIDE -apbridge dtimperiod 1 bintval 100 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff00 bridge0: flags=8043 mtu 1500 ether ac:de:48:da:2b:db priority 32768 hellotime 2 fwddelay 15 maxage 20 member: ath1 flags=7 port 2 priority 128 path cost 55 forwarding member: ath0 flags=3 A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
acpi: bad read from port / bad write to port
I cvsupped my source to RELENG_6 yesterday, built the world and kernel and rebooted into the new kernel in single user mode to test it out. Boot messages had a series of messages such as: acpi: bad write to port 0xcf8 (32), val 0x80003884 acpi: bad read from port 0xcfc (32) These messages do not occur with my present system, which is 6.1-STABLE from May 9th, 2006. Some googling seems to hint that MFC of src/sys/dev/acpica/Osd/OsdHardware.c as of May 11, 2006 *may* have something to do with it. But I am not a developer enough to understand whether these messages are merely cosmetic or should something be done to fix them. The machine where this is occurring is based on Chaintech 7AJA/0 motherboard with AMD Duron 800 MHz CPU. The verbose boot log is at http://www.raad.tartu.ee/~toomas/bootlog.txt -- Toomas Aas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FTP - Large file transfers (6.1)
On Tue, 2006-06-06 at 16:17 +0300, Iassen Anadoliev wrote: > On Tue, June 6, 2006 2:51 pm, David Samms wrote: > > I am having repeated FTP failures while transferring a 4G file across a > > LAN. Swapped out the switch, cables, and NIC's so don't believe hardware > > is involved. Have tried the default FTP server as well as vsftp and > > pure-ftp with the same results. NICs tested are em, sk, and rl. > > > > How to duplicate failure: Take two 6.1 machines with a 100M lan or > > x-talk cable and try to FTP a DVD image. The transfer fails around 90% > > of the time with > > "450 Error during write to data connection" > > > > We have a similar problem when using samba. The failure is not as > > consistent but always occurs under heavy load. Here is the error: > > > > [2006/06/04 22:20:02, 0] lib/util_sock.c:write_data(557) > > write_data: write failure in writing to client 192.168.163.41. Error > > Host is down > > > > It appears, that the network connection on the server is being reset, > > but why? And where or how do I find more information? > > > > > Can you look here: > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=110247+0+archive/2006/freebsd-net/20060205.freebsd-net > The attached patch solved my problem. A temporary workaround was to use > ProFTPD. Thank you for your reply. I patched the two files and rebuild world, the kernel, and pureFTP. I have retested the default FTP and pureFTP with the same failure. Anyone know how I can get more debug info? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dual Opteron system will not run SMP
On Tue, Jun 06, 2006 at 12:37:58PM +0100 I heard the voice of Pete French, and lo! it spake thus: > > I had been wondering what 'safe' does differently, and whether I > could fill up loader.conf with approrpiate values to emulate what > 'safe' does and then start commenting them out one at a time. "Safe" disables ATA/ATAPI DMA (so wouldn't affect SCSI), disables ACPI, and disables the APIC (which has the side effect of disabling SMP). -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
loader and ifconfig_*_name problem in 6.1-STABLE of 5 June
I upgraded via build/installworld from 6.1-PRERELEASE as of 27 Mars to 6.1-STABLE 5 June, and encounterd 2 problems. a) loader and kernel has some problem that lead to instant reboot upon loading the kernel. the problem was as follows: 1) booting the new kernel with the old loader was fine. I did buildkernel and installkernel and rebooted in single user mode. It had no problems. 2) loading the new kernel with the new loader made the machine reboot. After step (1), I did installworld and rebooted. It resulted in rebooting just after loader menu. I could escape to loader prompt and found that doing > unload > load kernel makes the machine reboot. 3) loading the old kernel with the new loader can boot in single user mode. > unload > set module_path=/boot/kernel.old > load kernel (and some other necessary modules) > boot -s was fine (though, exiting in multi-user mode had problem around mountd and panic'ed with the new userland). I copied the old /boot/loader.old to /boot/loader as a workaround. I have CFLAGS= -O2 -pipe COPTFLAGS= -O2 -pipe and no CPUTYPE setting in /etc/make.conf, so I wonder what caused the problem. b) pre-loading ng_ether.ko module and doing ifconfig name may have problem with ppp. I put the following in /etc/rc.conf ifconfig_sis0_name="net0" and changed device setting in /etc/ppp/ppp.conf as follows: set device PPPoE:net0 This did not work and had the following error message in /var/log/messages: ppp[258]: tun0: Warning: net0: Cannot send a netgraph message: No such file or directory changing device setting to set device PPPoE:sis0 or doing ngctl name sis0: net0 could make ppp work. The problem may be caused by loading ng_ether.ko in loader.conf (I do not remember why I did this, though). If I did not do that, ng_ether module was loaded when ppp was invoked after interface rename and might have no problem. I did not verify this yet, though. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: loader and ifconfig_*_name problem in 6.1-STABLE of 5 June
Hiroo Ono wrote: I upgraded via build/installworld from 6.1-PRERELEASE as of 27 Mars to 6.1-STABLE 5 June, and encounterd 2 problems. [ .. snip .. ] I copied the old /boot/loader.old to /boot/loader as a workaround. I have CFLAGS= -O2 -pipe COPTFLAGS= -O2 -pipe Please remove these and re-test. The default is "-O2 -fno-strict-aliasing" which generates slightly different code in some instances, -- Michael Butler, CISSP Security Architect Protected Networks http://www.protected-networks.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: quota and snapshots in 6.1-RELEASE
Scott Long wrote: Dmitriy Kirhlarov wrote: Hi! On Tue, May 23, 2006 at 04:35:21PM -0400, Kris Kennaway wrote: 6.1-STABLE after 6.1-RELEASE is releases. So I think you may want If you use snapshots with your quotas, update to 6.1-STABLE. If you Sorry, guys. You are mean RELENG_6_1 or RELENG_6? WBR RELENG_6. However, the changes will likely make their way into RELENG_6_1 in a few weeks as part of an errata update. Scott I have just done tests on 6.1-R and RELENG_6 as of yesterday evening. Unfortunately both still lock up hard, no crash, just a frozen system. I cant enter the KDB (ddb) via the console, but its unusable, as it wont let me type in anything. There must be some other change in -CURRENT that fixes this, as -CURRENT did not freeze during my previous tests. Just to confirm, here is the ID of ufs_quota.c on my RELENG_6 system: /usr/src/sys/ufs/ufs/ufs_quota.c: $FreeBSD: src/sys/ufs/ufs/ufs_quota.c,v 1.74.2.4 2006/05/14 00:23:27 tegge Exp $ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FTP - Large file transfers (6.1)
> Can you look here: > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=110247+0+archive/2006/freebsd-net/20060205.freebsd-net > The attached patch solved my problem. A temporary workaround was to use > ProFTPD. Well, after testing SAMBA I would have to say the patch improved things. I can now successfully transfer a 4G file unless the client is performing multiple file downloads. FTP from WindowsXP can almost get a 4G file. Gets to 70-95% and dumps. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FTP - Large file transfers (6.1)
On Tue, 6 Jun 2006, David Samms wrote: > > I patched the two files and rebuild world, the kernel, and pureFTP. > I have retested the default FTP and pureFTP with the same failure. > > Anyone know how I can get more debug info? Have you attempted the same FTP test over loopback using local filesystems only, to eliminate external network factors and NIC driver faults? -- Brian Tao, Luxography http://www.luxography.ca/ (main) http://blog.luxography.ca/ (blog) "The art of light" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: quota and snapshots in 6.1-RELEASE
On Tue, Jun 06, 2006 at 01:49:04PM -0400, Mike Jakubik wrote: > Scott Long wrote: > >Dmitriy Kirhlarov wrote: > > > >>Hi! > >> > >>On Tue, May 23, 2006 at 04:35:21PM -0400, Kris Kennaway wrote: > >> > >> > >>6.1-STABLE after 6.1-RELEASE is releases. So I think you may want > >>> > >>>If you use snapshots with your quotas, update to 6.1-STABLE. If you > >> > >> > >>Sorry, guys. You are mean RELENG_6_1 or RELENG_6? > >> > >>WBR > > > >RELENG_6. However, the changes will likely make their way into > >RELENG_6_1 in a few weeks as part of an errata update. > > > >Scott > > I have just done tests on 6.1-R and RELENG_6 as of yesterday evening. > Unfortunately both still lock up hard, no crash, just a frozen system. I > cant enter the KDB (ddb) via the console, but its unusable, as it wont > let me type in anything. There must be some other change in -CURRENT > that fixes this, as -CURRENT did not freeze during my previous tests. > > > Just to confirm, here is the ID of ufs_quota.c on my RELENG_6 system: > > /usr/src/sys/ufs/ufs/ufs_quota.c: > $FreeBSD: src/sys/ufs/ufs/ufs_quota.c,v 1.74.2.4 2006/05/14 > 00:23:27 tegge Exp $ The hangs are mostly related to snapshots. It would be better to update to the latest RELENG_6. Hangs on RELENG_6_1 is not so much interesting. For hanged RELENG_6 system, please do what described below and post the log of the ddb session. I'm not sure whether kbdmux was MFCed into RELENG_6 (AFAIR, yes). If you have it in your kernel, add the line hint.kbdmux.0.disabled="1" into the /boot/device.hints to make ddb usable. After that, on the hang, enter ddb, and do ps and tr for all suspected processes. Better yet, add the following options to your kernel: options INVARIANTS options INVARIANT_SUPPORT options WITNESS options DEBUG_LOCKS options DEBUG_VFS_LOCKS options DIAGNOSTIC and, after hang, do in ddb show allpcpu show alllocks show lockedvnods ps For each process mentioned in show output, do where (for threaded processes, do thread ; where). BTW, it would be great to add this instructions to the FAQ. pgpW6ly4sc0lu.pgp Description: PGP signature
Re: quota and snapshots in 6.1-RELEASE
On Tue, Jun 06, 2006 at 09:22:34PM +0300, Konstantin Belousov wrote: > The hangs are mostly related to snapshots. It would be better to > update to the latest RELENG_6. I need to clarify this no so wise statement made at the end of the day. It is believed that Tor Egge fixed all known cases of deadlocks related to shapshots. From all that situations (around of ten), only one required presence of active quotas and snapshot. All fixes are MFCed to the RELENG_6. So, the interesting reports on the deadlocks shall be done against RELENG_6, not RELENG_6_1 (until errata for snapshots is issued). Guys, sorry for embarassing statement. pgpi7huWVoMiy.pgp Description: PGP signature
Re: FTP - Large file transfers (6.1)
On Tue, 2006-06-06 at 14:19 -0400, Brian Tao wrote: > On Tue, 6 Jun 2006, David Samms wrote: > > > > I patched the two files and rebuild world, the kernel, and pureFTP. > > I have retested the default FTP and pureFTP with the same failure. > > > > Anyone know how I can get more debug info? > > Have you attempted the same FTP test over loopback using local > filesystems only, to eliminate external network factors and NIC driver > faults? Ran four FTP transfers through lo0 without a failure. I am not sure how much that proves. Guess if conditions are perfect a ftp transfer can succeed. Has anyone tried to duplicate my problem on a LAN? Not sure how this could be related to hardware, but am setting up two other machines as client/server with a new x-talk cable. Also will run FreeBSD 5.4 on my original setup. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How can I know which files a proccess is accessing?
Hello, I need to know which files under /var a proccess (httpd here) is acessing. It is not logs because I have a different partition for logs. gstat tells me that slice ad0s1h (my /var) is 100% frequently, and in fact with fstat I can see a number of httpd proccesses running accesing that. But fstat only shows me inodes and the mount point. I need to know which files the proccesses are acessing. How? Thank you. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
On Jun 06, Eduardo Meyer wrote: > I need to know which files under /var a proccess (httpd here) is > acessing. It is not logs because I have a different partition for > logs. > > gstat tells me that slice ad0s1h (my /var) is 100% frequently, and in > fact with fstat I can see a number of httpd proccesses running > accesing that. But fstat only shows me inodes and the mount point. > > I need to know which files the proccesses are acessing. Linux has a cool program: lsof (list open files). Does FreeBSD have something similar? -Clint ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
On Tue, Jun 06, 2006 at 05:39:34PM -0300, Eduardo Meyer wrote.. > Hello, > > I need to know which files under /var a proccess (httpd here) is > acessing. It is not logs because I have a different partition for > logs. > > gstat tells me that slice ad0s1h (my /var) is 100% frequently, and in > fact with fstat I can see a number of httpd proccesses running > accesing that. But fstat only shows me inodes and the mount point. > > I need to know which files the proccesses are acessing. lsof? $ lsof /var COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME mutt8018 wb4r VREG 0,172 163763 47112 /var/mail/wb sh 8024 wb4r VREG 0,172 163763 47112 /var/mail/wb vi 8025 wb4r VREG 0,172 163763 47112 /var/mail/wb sh 8031 wb4r VREG 0,172 163763 47112 /var/mail/wb $ -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
On 6/6/06, David Wolfskill <[EMAIL PROTECTED]> wrote: You may find the "lsof" port useful for answering such questions. I tried it, but it seems that I found some limitations: lsof: no local file space at PID 16543 # ps 16543 PID TT STAT TIME COMMAND 16543 ?? S 0:02.43 /usr/local/sbin/httpd -k start -DSSL Any tuning would do the job? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
Hi On Tue, Jun 06, 2006 at 17:39 (-0300), Eduardo Meyer wrote: > Hello, > > I need to know which files under /var a proccess (httpd here) is > acessing. It is not logs because I have a different partition for > logs. > > gstat tells me that slice ad0s1h (my /var) is 100% frequently, and in > fact with fstat I can see a number of httpd proccesses running > accesing that. But fstat only shows me inodes and the mount point. > > I need to know which files the proccesses are acessing. > > How? Try with lsof from ports. /Johan K > > Thank you. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Johan Karlsson mailto:[EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
"Eduardo Meyer" <[EMAIL PROTECTED]> writes: > gstat tells me that slice ad0s1h (my /var) is 100% frequently, and in > fact with fstat I can see a number of httpd proccesses running > accesing that. But fstat only shows me inodes and the mount point. > > I need to know which files the proccesses are acessing. > > How? Map the inodes to files with find(1)? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
On Tue, 06 Jun 2006 23:14:01 +0200, Clint Olsen <[EMAIL PROTECTED]> wrote: On Jun 06, Eduardo Meyer wrote: I need to know which files under /var a proccess (httpd here) is acessing. It is not logs because I have a different partition for logs. gstat tells me that slice ad0s1h (my /var) is 100% frequently, and in fact with fstat I can see a number of httpd proccesses running accesing that. But fstat only shows me inodes and the mount point. I need to know which files the proccesses are acessing. Linux has a cool program: lsof (list open files). Does FreeBSD have something similar? /usr/ports/sysutils/lsof -- Ronald Klop Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
On 6/6/06, pete wright <[EMAIL PROTECTED]> wrote: On 6/6/06, Eduardo Meyer <[EMAIL PROTECTED]> wrote: > Hello, > > I need to know which files under /var a proccess (httpd here) is > acessing. It is not logs because I have a different partition for > logs. > > gstat tells me that slice ad0s1h (my /var) is 100% frequently, and in > fact with fstat I can see a number of httpd proccesses running > accesing that. But fstat only shows me inodes and the mount point. > > I need to know which files the proccesses are acessing. > if you can get fstat to help you may want to take a look at lfof, sorry that should be lsof -pete -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
On Tue, Jun 06, 2006 at 02:14:01PM -0700, Clint Olsen wrote: > ... > > I need to know which files the proccesses are acessing. > > Linux has a cool program: lsof (list open files). Does FreeBSD have > something similar? lsof never has been Linux-specific. Please see sysutils/lsof in your local ports tree. Peace, david -- David H. Wolfskill [EMAIL PROTECTED] Doing business with spammers only encourages them. Please boycott spammers. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpIIHyISESxD.pgp Description: PGP signature
Re: How can I know which files a proccess is accessing?
On Tue, Jun 06, 2006 at 02:14:01PM -0700, Clint Olsen wrote.. > On Jun 06, Eduardo Meyer wrote: > > I need to know which files under /var a proccess (httpd here) is > > acessing. It is not logs because I have a different partition for > > logs. > > > > gstat tells me that slice ad0s1h (my /var) is 100% frequently, and in > > fact with fstat I can see a number of httpd proccesses running > > accesing that. But fstat only shows me inodes and the mount point. > > > > I need to know which files the proccesses are acessing. > > Linux has a cool program: lsof (list open files). Does FreeBSD have > something similar? The same: [EMAIL PROTECTED] ~: pkg_info | grep lsof lsof-4.76.2 Lists information about open files (similar to fstat(1)) see: /usr/ports/sysutils/lsof -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
On Tue, Jun 06, 2006 at 02:14:01PM -0700 I heard the voice of Clint Olsen, and lo! it spake thus: > > Linux has a cool program: lsof (list open files). Does FreeBSD have > something similar? fstat. (or lsof in ports, if you wanted) -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
On 6/6/06, Eduardo Meyer <[EMAIL PROTECTED]> wrote: Hello, I need to know which files under /var a proccess (httpd here) is acessing. It is not logs because I have a different partition for logs. gstat tells me that slice ad0s1h (my /var) is 100% frequently, and in fact with fstat I can see a number of httpd proccesses running accesing that. But fstat only shows me inodes and the mount point. I need to know which files the proccesses are acessing. if you can get fstat to help you may want to take a look at lfof, available in ports: /usr/ports/sysutils/lsof " Lsof (LiSt Open Files) lists information about files that are open by the running processes. An open file may be a regular file, a directory, a block special file, a character special file, an executing text reference, a library, a stream or a network file (Internet socket, NFS file or Unix domain socket). " -pete -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
On 6/6/06, Eduardo Meyer <[EMAIL PROTECTED]> wrote: Hello, I need to know which files under /var a proccess (httpd here) is acessing. It is not logs because I have a different partition for logs. [...] check out ./ports/sysutils/lsof. An excellent little util that has become a standard on all of my *NIXish installs. It'll tell you all you ever wanted to know (and more) about which pieces of your OS are touching what. -- Stephen Spencer Lawrence, KS "If God dropped acid, would he see people?" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
On Tuesday 06 June 2006 05:14 pm, Clint Olsen wrote: > On Jun 06, Eduardo Meyer wrote: > > I need to know which files under /var a proccess (httpd here) is > > acessing. It is not logs because I have a different partition for > > logs. > > > > gstat tells me that slice ad0s1h (my /var) is 100% frequently, > > and in fact with fstat I can see a number of httpd proccesses > > running accesing that. But fstat only shows me inodes and the > > mount point. > > > > I need to know which files the proccesses are acessing. > > Linux has a cool program: lsof (list open files). Does FreeBSD > have something similar? http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/lsof/ Jung-uk Kim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
On Tue, 6 Jun 2006, Clint Olsen wrote: > > Linux has a cool program: lsof (list open files). Does FreeBSD have > something similar? % cd /usr/ports % make search name=lsof Port: lsof-4.76.1.1 Path: /usr/ports/sysutils/lsof Info: Lists information about open files (similar to fstat(1)) Maint: [EMAIL PROTECTED] B-deps: R-deps: WWW:http://people.freebsd.org/~abe/ -- Brian Tao, Luxography http://www.luxography.ca/ (main) http://blog.luxography.ca/ (blog) "The art of light" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
Clint Olsen wrote:
Linux has a cool program: lsof (list open files). Does FreeBSD have
something similar?
Yes, 'fstat'. Though I very rarely remember its name ('lsof' is far more
memorable, IMHO).
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
Eduardo Meyer wrote: Hello, I need to know which files under /var a proccess (httpd here) is acessing. It is not logs because I have a different partition for logs. Is everyone forgetting the command "fstat" that comes with freebsd? :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: loader and ifconfig_*_name problem in 6.1-STABLE of 5 June
At Tue, 06 Jun 2006 13:17:38 -0400, Michael Butler wrote: > > Hiroo Ono wrote: > > I upgraded via build/installworld from 6.1-PRERELEASE as of 27 Mars > > to 6.1-STABLE 5 June, and encounterd 2 problems. > > [ .. snip .. ] > > > I copied the old /boot/loader.old to /boot/loader as a workaround. > > I have > > CFLAGS= -O2 -pipe > > COPTFLAGS= -O2 -pipe > > Please remove these and re-test. The default is "-O2 -fno-strict-aliasing" > which generates slightly different code in some instances, Thank you. I commented out above two lines from /etc/make.conf and did build/installkernel, build/installworld again (a little superfluous maybe). So, the loader and the kernel must be built with default options. The result was same. Loading new kernel with the new loader reboots the machine. The CPU is an athlon (CPU lines from dmesg were as follows). I do not remember what was the chipset now; CPU: AMD Athlon(tm) XP 1600+ (1403.19-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 Features=0x383fbff AMD Features=0xc0480800 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: carp with IPv6 broken on 6.1-RELEASE
Hi, Philippe Pegon wrote: > it seems that carp is broken on FreeBSD 6.1-RELEASE when an inet6 > address is configured on a carp interface. Since I upgraded from 6.0 > to 6.1 (today) I can't see IPv6 carp advertisement with tcpdump. > > Did someone else observe this ? I think I just did, or something similar/related. I just upgraded the 'master' of 2 machines to 6.1 (where the backup was already running 6.1 for a couple of days) and now I see my carp session 'flapping'. The master machine kept running master, the backup was switching to master once every 5 seconds I think, stealing some traffic and notifying me with: kernel: carp0: MASTER -> BACKUP (more frequent advertisement received) ... which of course is not true. I'm sure there is no firewall in the way (in fact I disabled it for a short while), I saw the vrrp advertisements (while the error occurs I see the machine that is suppost to be backup sending one advertisement every 4/5 seconds as well)... this config was running before, I'm confident there is something wrong. As soon as I remove the IPv6 address from the interface everything seems to work fine, role only switches when there's a reason for it. Philippe, did you create a pr? Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Suggestions for Adaptec SAS AIC9410
The mpt driver was just MFC'd, but that won't help the adaptec issue. There is a remote chance that somebody I'm doing work for will want a FreeBSD driver for the adaptec card, but that won't be for a couple of months. It's a huge PITA- the SuperMicro boards are nice , but they don't get along with LSI-Logic. So, when I get SuperMicro, I pretty much get the ones with native SATA. On 6/5/06, Andy Dills <[EMAIL PROTECTED]> wrote: I'm trying to get a Supermicro 6024H-32R setup with 6.1, but I'm discovering that the Adaptec SAS AIC9410 controller isn't yet supported. I see one brief thread about it on this mailing list back in March, but no further mention or conclusive details. There was talk of MFCing the mpt driver...is anybody using this in production? I'd prefer to use FreeBSD, but I'm guessing I'm going to need to do SuSE for this box, which Adaptec provides drivers for. Thanks, Andy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 --- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1 kernel unable to find /dev ?
Brian Tao wrote: On Sun, 4 Jun 2006, Gary Palmer wrote: On Sat, Jun 03, 2006 at 11:35:29PM -0400, Brian Tao wrote: errno 8 is ENOEXEC and 13 is EACCES... but: Silly question: /sbin/init has the "x" flag set, correct? It should be mode 0500 (i.e. -r-x--) Yep... # ls -ld / /sbin /sbin/init drwxr-xr-x 21 root wheel 512 Jun 3 21:43 / drwxr-xr-x 2 root wheel2560 May 4 18:05 /sbin -r-x-- 1 root wheel 582560 May 4 18:05 /sbin/init This is the same /sbin/init that the 6.0 kernel has no problems executing, but the 6.1's do (if booting into "safe" or noacpi mode). Hi Brian, The only other thing I can suggest is to boot single user and run a manual full fsck incase the metadata is confused somehow. Also it might be worthwhile checking that the MBR and partition tables are sane. Assuming that when you added the drives, you didn't change the kernel until after you started having problems, the only thing I can figure is there was some minor corruption somewhere. Regards ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
"Eduardo Meyer" <[EMAIL PROTECTED]> writes: > On 6/6/06, David Wolfskill <[EMAIL PROTECTED]> wrote: >> You may find the "lsof" port useful for answering such questions. >> > > I tried it, but it seems that I found some limitations: > > lsof: no local file space at PID 16543 > > # ps 16543 > PID TT STAT TIME COMMAND > 16543 ?? S 0:02.43 /usr/local/sbin/httpd -k start -DSSL > > Any tuning would do the job? Are you running with tightened up security that might prevent fstat from accessing /dev/kmem? I don't know fstat failures from experience or what causes it to just show inode numbers - perhaps delete files that are still open. I'm unsure about the reason for lsof's complaint; if you installed a package, try rebuilding the port. Something different, if fstat and lsof continue to fail: you may try attaching a syscall tracer such as truss, ktrace or strace (the latter from ports) to the process and see if it leaks file descriptors. This may fail due to permissions however. -- Matthias Andree ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Error while 'make buildworld' in terminal.o
Good present! A was synchronise my source to RELENG_5_3 by cvsup. When I was starting build world (make buildworld), building process was broken with output: cc -O2 -pipe -DINFODIR=\"/usr/share/info:/usr/local/info:/usr/X11R6/info:.\" -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/info/../../../../contrib/texinfo -I/usr/src/gnu/usr.bin/texinfo/info/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/gnu/usr.bin/texinfo/info/../../../../contrib/texinfo/info/window.c cc -O2 -pipe -DINFODIR=\"/usr/share/info:/usr/local/info:/usr/X11R6/info:.\" -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/info/../../../../contrib/texinfo -I/usr/src/gnu/usr.bin/texinfo/info/../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/legacy/usr/include -static -L/usr/obj/usr/src/i386/legacy/usr/lib -o info dir.o display.o doc.o dribble.o echo-area.o filesys.o footnotes.o gc.o indices.o info-utils.o info.o infodoc.o infomap.o m-x.o man.o nodemenu.o nodes.o search.o session.o signals.o terminal.o tilde.o variables.o window.o -ltermcap /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/texinfo/info/../libtxi/libtxi.a -legacy terminal.o(.text+0xa3): In function `terminal_goto_xy': : undefined reference to `tgoto' terminal.o(.text+0xac): In function `terminal_goto_xy': : undefined reference to `tputs' terminal.o(.text+0x142): In function `terminal_clear_to_eol': : undefined reference to `tputs' terminal.o(.text+0x176): In function `terminal_clear_screen': : undefined reference to `tputs' terminal.o(.text+0x1aa): In function `terminal_up_line': : undefined reference to `tputs' terminal.o(.text+0x1de): In function `terminal_down_line': : undefined reference to `tputs' terminal.o(.text+0x212): more undefined references to `tputs' follow terminal.o(.text+0x30f): In function `terminal_delete_lines': : undefined reference to `tgoto' terminal.o(.text+0x318): In function `terminal_delete_lines': : undefined reference to `tputs' terminal.o(.text+0x37a): In function `terminal_insert_lines': : undefined reference to `tputs' terminal.o(.text+0x3ab): In function `terminal_insert_lines': : undefined reference to `tgoto' terminal.o(.text+0x3b4): In function `terminal_insert_lines': : undefined reference to `tputs' terminal.o(.text+0x547): In function `terminal_get_screen_size': : undefined reference to `tgetnum' terminal.o(.text+0x593): In function `terminal_get_screen_size': : undefined reference to `tgetnum' terminal.o(.text+0x621): In function `terminal_initialize_terminal': : undefined reference to `tgetent' terminal.o(.text+0x63d): In function `terminal_initialize_terminal': : undefined reference to `tgetstr' terminal.o(.text+0x649): In function `terminal_initialize_terminal': : undefined reference to `BC' terminal.o(.text+0x659): In function `terminal_initialize_terminal': : undefined reference to `PC' terminal.o(.text+0x690): In function `terminal_initialize_terminal': : undefined reference to `ospeed' terminal.o(.text+0x6a1): In function `terminal_initialize_terminal': : undefined reference to `tgetstr' terminal.o(.text+0x6b6): In function `terminal_initialize_terminal': : undefined reference to `tgetstr' terminal.o(.text+0x6c8): In function `terminal_initialize_terminal': : undefined reference to `tgetstr' terminal.o(.text+0x6da): In function `terminal_initialize_terminal': : undefined reference to `tgetstr' terminal.o(.text+0x6ec): In function `terminal_initialize_terminal': : undefined reference to `tgetstr' terminal.o(.text+0x6fe): more undefined references to `tgetstr' follow terminal.o(.text+0x85b): In function `terminal_initialize_terminal': : undefined reference to `tgetflag' terminal.o(.text+0x89f): In function `terminal_initialize_terminal': : undefined reference to `tgetstr' terminal.o(.text+0x8b4): In function `terminal_initialize_terminal': : undefined reference to `tgetstr' terminal.o(.text+0x8c6): In function `terminal_initialize_terminal': : undefined reference to `tgetstr' terminal.o(.text+0x8d8): In function `terminal_initialize_terminal': : undefined reference to `tgetstr' terminal.o(.text+0x8ea): In function `terminal_initialize_terminal': : undefined reference to `tgetstr' terminal.o(.text+0x8fc): more undefined references to `tgetstr' follow terminal.o(.text+0xaaf): In function `terminal_initialize_terminal': : undefined reference to `ospeed' terminal.o(.text+0xad5): In function `terminal_initialize_terminal': : undefined reference to `tgetflag' terminal.o(.text+0xb02): In function `terminal_initialize_terminal': : undefined reference to `tgetstr' terminal.o(.text+0xb17): In function `terminal_initialize_terminal': : undefined reference to `tgetstr' terminal.o(.text+0xb32): In function `terminal_initialize_terminal': : undefined reference to `tgetstr' terminal.o(.text+0xc96): In function `terminal_prep_terminal': : undefined reference to `tputs' terminal.o(.text+0xd3e): In function `terminal_prep_terminal'
Re: FTP - Large file transfers (6.1)
On Tue, 2006-06-06 at 14:19 -0400, Brian Tao wrote: > On Tue, 6 Jun 2006, David Samms wrote: > > > > I patched the two files and rebuild world, the kernel, and pureFTP. > > I have retested the default FTP and pureFTP with the same failure. > > > > Anyone know how I can get more debug info? > > Have you attempted the same FTP test over loopback using local > filesystems only, to eliminate external network factors and NIC driver > faults? I brought in a new machine and built it with 6.1 i386 and tested then again with AMD64 and retested. FTP transfers from the new server are always successful even with the the same network card, switch, and cables. Thanks for your help. I am considering the issue resolved. Guess my test box is a bit flaky. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Error while 'make buildworld' in terminal.o
When I was starting build world (make buildworld), building process was broken with output: [snip] # make cleandepends # make cleanworld Remove the contents of /usr/obj completely and try again? -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re[2]: Error while 'make buildworld' in terminal.o
>> When I was starting build world (make buildworld), building >> process was broken with output: Joseph> [snip] >> # make cleandepends >> # make cleanworld Joseph> Remove the contents of /usr/obj completely and try again? Yes. I did it every time, before making. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
Eduardo Meyer wrote:
Hello,
I need to know which files under /var a proccess (httpd here) is
acessing. It is not logs because I have a different partition for
logs.
gstat tells me that slice ad0s1h (my /var) is 100% frequently, and in
fact with fstat I can see a number of httpd proccesses running
accesing that. But fstat only shows me inodes and the mount point.
I need to know which files the proccesses are acessing.
find(1) can match inodes. A quick example:
> fstat | grep 'httpd.*/var ' | awk '{print $6}' | xargs -n 1 sudo find
-x /var -inum | sort -u
/var/log/httpd-error.log
/var/run/accept.lock.#
/var/tmp/apr8530d5
/var/tmp/aprF2Zs0e
--
Darren Pilgrim
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Messages from rc-scripts are not displayed at all
Hello. > > The problem is much more complex, I suppose. Not only > > rc-scripts messages aren't display, there are no messages at > > all, from any scripts and programs, started between kernel > > boot and login prompt. > > Strange. > > - What does ls -la /dev/console show? 0 crw--- 1 root wheel 0,23 7 Jun 09:50 /dev/console > - Does a single user boot (boot -s) drop you to a 'normal' >shell? No. Right after kernel messages there is nothing displayed (no command prompt, nothing at all). > - Does a serial console work normally? PC with a problem is a notebook without COM-port. -- .O. | Sergei Mozhaisky ..O | http://frenzy.org.ua/ OOO | http://frenzytechnix.livejournal.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Messages from rc-scripts are not displayed at all
Do you have a /boot.config file? If so, delete it. Also, try enabling console logging in /etc/syslog.conf, and see if you get anything there. hth, Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
