msdosfs performance unbearable
ufs: $ time -h tar -xf php_manual_en.tar.gz 3.31s real 0.43s user 0.51s sys msdosfs: I stopped that after 45 minutes. Also the system becomes barely responsive. The mouse moves extremely sloppy and a key-press often causes 2 characters to be printed. Mouse-clicks are either lost or take more than 10 seconds to be recognized. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
cryptodev and ssh on RELENG_7
Hello, I have a HiFN crypto card and can remember that it was used for ssh connections with 3des encryption (on 6.1 afair). But with RELENG_7 it isn't used at all (no interrupts) if I 'ssh -v -c 3des-cbc [EMAIL PROTECTED]' Any ideas what is wrong? dmesg: hifn0 mem 0x8000-0x8fff,0x8004-0x80041fff,0x8008-0x80087fff irq 12 at device 13.0 on pci0 hifn0: [ITHREAD] hifn0: Hifn 7955, rev 0, 32KB dram, pll=0x801ext clk, 4x mult crw-rw-rw- 1 root wheel - 0, 41 Nov 27 08:13:41 2007 /dev/crypto Thanks in advance, -Harry signature.asc Description: PGP signature
Re: installation problems of FreeBSD 7 beta 2 on Dell D610 (multiboot con solaris, linux, winxp)
On 11/27/07, Dennis Melentyev [EMAIL PROTECTED] wrote: Hi! 2007/11/27, Stefano Spinucci [EMAIL PROTECTED]: I encountered some problems installing FreeBSD 7 beta 2 on my Dell D610 laptop, on the original 60 gb hd; the hd is formatted as follows: - primary 1, 15 gb, ntfs for Windows XP - primary 2, 15 gb, solaris for Open Solaris - primary 3, 10 gb, fat32 for FreeBSD - extended, 20 gb, 3 partitions for linux I tried to install FreeBSD many times, but after the geometry error (the geometry is however correctly recognized), FDISK doesn't find any partition and the space is shown as free, unpartitioned. I tried to set the partition type for FreeBSD to FAT16, FAT32, FreeBSD and I also reformatted the partition many times, but with no success. have you any idea??? Are you kidding? If no, just read the handbook. And check the partition type for FreeBSD. FAT[13][26] is for MustDie. -- Dennis Melentyev I'm not kidding. I read the handbook before installing, before writing this emai and now and, correct me if I'm wrong, FDISK should recognize existent primary partitions; then, *inside* FDISK, I can format the primary partiton (for me #3) for FreeBSD. from section 2.6.2 of the Hankbook The second section [of FDISK] shows the slices that are currently on the disk, where they start and end, how large they are, the name FreeBSD gives them, and their description and sub-type. Then I repeat my question: why FDISK shows my disk (with 3 primary partitions and an extended partition) as a single block of unused space ??? If you have some useful ideas (and not, RTFManual/MailingList is not an useful idea) please reply me. thanks --- Stefano Spinucci ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: installation problems of FreeBSD 7 beta 2 on Dell D610 (multiboot con solaris, linux, winxp)
HI Stefano! 2007/11/27, Stefano Spinucci [EMAIL PROTECTED]: On 11/27/07, Dennis Melentyev [EMAIL PROTECTED] wrote: Hi! 2007/11/27, Stefano Spinucci [EMAIL PROTECTED]: I encountered some problems installing FreeBSD 7 beta 2 on my Dell D610 laptop, on the original 60 gb hd; the hd is formatted as follows: - primary 1, 15 gb, ntfs for Windows XP - primary 2, 15 gb, solaris for Open Solaris - primary 3, 10 gb, fat32 for FreeBSD - extended, 20 gb, 3 partitions for linux I tried to install FreeBSD many times, but after the geometry error (the geometry is however correctly recognized), FDISK doesn't find any partition and the space is shown as free, unpartitioned. I tried to set the partition type for FreeBSD to FAT16, FAT32, FreeBSD and I also reformatted the partition many times, but with no success. have you any idea??? Are you kidding? If no, just read the handbook. And check the partition type for FreeBSD. FAT[13][26] is for MustDie. -- Dennis Melentyev I'm not kidding. I read the handbook before installing, before writing this emai and now and, correct me if I'm wrong, FDISK should recognize existent primary partitions; then, *inside* FDISK, I can format the primary partiton (for me #3) for FreeBSD. Well, one of us are just using different terminology then. 0. FAT* is not a right filesystem type for FreeBSD. It must be UFS/UFS2 1. Geometry is what you BIOS think what should it be. Not the numbers on device label. 2. Sysinstall is NOT fdisk. It has some functionality though. So, find out what geometry is used by BIOS for you disk and supply it before any access to slices. PS. There are some reports on local mailing lists about problems with sysinstall's fdisk. Try just real fdisk, disklabel and newfs instead (man fdisk disklabel newfs for details). PPS. Nevertheless, handbook and man pages are a mandatory for all this issues. from section 2.6.2 of the Hankbook The second section [of FDISK] shows the slices that are currently on the disk, where they start and end, how large they are, the name FreeBSD gives them, and their description and sub-type. Then I repeat my question: why FDISK shows my disk (with 3 primary partitions and an extended partition) as a single block of unused space ??? Well, this is much more clean problem description. Fix your geometry. Also, if disks are not ATA/SATA, state this. If you have some useful ideas (and not, RTFManual/MailingList is not an useful idea) please reply me. /me disagree here -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: installation problems of FreeBSD 7 beta 2 on Dell D610 (multiboot con solaris, linux, winxp)
Stefano Spinucci wrote: I encountered some problems installing FreeBSD 7 beta 2 on my Dell D610 laptop, on the original 60 gb hd; the hd is formatted as follows: - primary 1, 15 gb, ntfs for Windows XP - primary 2, 15 gb, solaris for Open Solaris - primary 3, 10 gb, fat32 for FreeBSD - extended, 20 gb, 3 partitions for linux I tried to install FreeBSD many times, but after the geometry error (the geometry is however correctly recognized), FDISK doesn't find any partition and the space is shown as free, unpartitioned. I tried to set the partition type for FreeBSD to FAT16, FAT32, FreeBSD and I also reformatted the partition many times, but with no success. have you any idea??? Stefano stable@ Your symptoms seem likely laptop specific, so if you remain stuck, later try mobile@ I saw similar installing 7.0-BETA3 on my Digital HiHote Ultra 2000 laptop: it recognised the 5G laptop disc, but did Not recognise the 3 x FreeBSD-5.1-RELEASE boot partitions that work OK there. So I thought, OK, abandon installing on an fdisk partition, install on whole disk. It went through partitioning, then failed to find its file system. 5.1 was still intact booted. I assume it's my laptop ATA interface, seen that problem before. FreeBSD for old hardware often needs extra instructions manually to loader to tell WD/ATA (/or ep0) to run in a more conservative mode. I'll look for right syntax. eg maybe hw.ata.ata_dma=0 etc starting in my http://www.berklix.com/~jhs/hardware/laptops/#loader.conf /Soapbox: This frequent `FreeBSD defaults to need high end modern hardware' is bad for publicity, newbies who dont know where to look will tell friends: I gave up went Linux. ( For those who might say buy high end, No! spare old laptop sufficient for Xterm + mp3 + LAN for stereo in living room, leaving main laptop free for more demanding things. Plus not all can afford latest, + conservation, green etc, ... just needs more generous install defaults. ) FreeBSD has improved elsewhere though on old hardware: The same laptop that failed to go beyond 5.1 without losing ep0, now sees ep0 in 7.0-BETA3 install. End Soapbox/ -- Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com Ihr Rauch = mein allergischer Kopfschmerz. Dump cigs 4 snuff. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Some processes stay active after killing its PID
Thanks for reply, I tried to kill the process via all possibilities described in man kill :) But I didn't know there are some processes which can't be killed, so I tried again running wdfs, but after ps -xacu | grep wdfs I see USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 971 73,9 0,9 19048 5552 ?? Rs1:03od 0:15,36 wdfs no D state :( I'm quite confused, because in state, I have to reboor every time I umount wdfs drive :( 2007/11/26, Roland Smith [EMAIL PROTECTED]: On Mon, Nov 26, 2007 at 04:30:01PM +0100, Honza Holakovsky wrote: Hi, I'm expecting quite curious problem (currently spotted with usage of audacious (1.3.2 [20070405-4320]) and fusefs-wdfs (1.3.2)) After I finish working with either of these two programs (i.e. closing audacious windown or unmounting wdfs unit), they still run on background, and cosume all remaining cpu performance. Even if I kill its PID, it's still running. top looks like this: How did you kill them? Did you use 'kill -9'? last pid: 21161; load averages: 1.30, 1.33, 1.11 up 0+02:49:43 16:20:56 51 processes: 3 running, 48 sleeping CPU states: 53.1% user, 0.0% nice, 46.5% system, 0.4% interrupt, 0.0%idle Mem: 209M Active, 226M Inact, 105M Wired, 21M Cache, 70M Buf, 54M Free Swap: 2048M Total, 20K Used, 2048M Free PID USERNAMETHR PRI NICE SIZERES STATETIME WCPU COMMAND 19163 root 1 1320 19112K 4948K RUN 14:57 81.88% wdfs 18873 holakac 1 960 79652K 53568K select 13:14 1.66% Xorg 18911 holakac 4 200 104M 81280K kserel 9:06 0.00%firefox-bin Under some circumstances, a process cannot be killed, e.g. if 'px -xacu' has the process in D state. See ps(1). Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Pthread scheduling in FreeBSD 7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I have a question concerning *pthread* scheduling with FreeBSD 7. My goal: I have a multi-threaded application, in which I have a thread that should get higher priority than the other threads. Realtime-Priority for this thread would be nice but is not necessary. My approach so far (which worked for FreeBSD 6.2): Use the libpthread implementation, use pthread_attr_setschedparam() to increase the priority (scope is PTHREAD_SCOPE_SYSTEM, policy is SCHED_RR). For the libpthread implemenation that worked fine and did just what I expected. I also tried it using libthr, but libthr didn't care about the priority. My prolbem in FreeBSD 7: The libpthread implementation seems to have gone and libthr is the default. However libthr still ignores the pthread scheduling parameters. (FreeBSD 7 has a different default priority and policy for libthr than FreeBSD 6 however). I also saw, that libkse is now available as a new M:N pthread implementation, so I tried using that. But libkse is significantly slower than libthr and libkse does not always schedule to all CPUs. As far as I can tell libkse only schedules to all CPUs if the load is small when the threads are created. I have never seen this behaviour with libpthread from FreeBSD 6. And libkse is quite unpredictable: I used a test program with 10 threads (with equal priority) and recorded the wall-runtime of each of them. The runtime of them differs by a factor of up to 5(!). I have to mention however, that I used different machines. The one running FreeBSD 6 is a dual-cpu AMD Athlon with 32bit OS, while the one running FreeBSD 7 is a dual-core Intel running a 64bit OS. In FreeBSD 6 I used SCHED_4BSD in the kernel, while I used SCHED_ULE in FreeBSD 7. My questions: * Can anyone shed some light on this issue? * How can I tune thread scheduling in FreeBSD 7? What happened to the libpthread implementation from FreeBSD 6? * What triggers the whether libkse schedules to only one or to all CPUs? Is this tuneable? * Do rtprio() and/or nice() work for single threads? * Any other ideas how I can assign a higher priority to a thread. Maybe even realtime priority? TIA Gregor - -- Gregor Maier [EMAIL PROTECTED] TU Berlin / Deutsche Telekom Labs [EMAIL PROTECTED] Sekr. TEL 4, FG INETwww.net.t-labs.tu-berlin.de Ernst-Reuter-Platz 7 10587 Berlin, Germany -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHTAQldGiwgbikMYMRAie+AKCVY2CxJEmmnPer2OhF6WavK8seZwCfYlVQ a49Oq0EUHJq/FnSfcb+0p5M= =xl8X -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Some processes stay active after killing its PID
On Tue, Nov 27, 2007 at 01:05:21PM +0100, Honza Holakovsky wrote: Thanks for reply, I tried to kill the process via all possibilities described in man kill :) But I didn't know there are some processes which can't be killed, so I tried again running wdfs, but after ps -xacu | grep wdfs I see USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 971 73,9 0,9 19048 5552 ?? Rs1:03od 0:15,36 wdfs no D state :( I'm quite confused, because in state, I have to reboor every time I umount wdfs drive :( Is it possible to truss or ktrace that process? It would be interesting to know what it's doing (re: chewing up 74% CPU). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em driver 6.6.6 regression
On Wed, Nov 07, 2007 at 12:55:24PM +0300, Igor Sysoev wrote: On Wed, Nov 07, 2007 at 12:18:06PM +0300, Igor Sysoev wrote: On Fri, Oct 12, 2007 at 04:15:46PM +0400, Igor Sysoev wrote: Yesterday I have cvsup'ed FreeBSD on ThinkPad T42 to RELENG_6 2007.10.10.23.59.59 and have noticed lags while playing mp3 and browsing. I have suspected new em driver, because there was no lags if wifi iwi0 was used instead of em0 for network. So I had downgraded the em driver separately to 6.2.9 version, have build a kernel loadable module, and have loaded it instead of the 6.6.6 module, and the lags have disappeared. The lags appeares only if browser (Firefox, Opera) does several requests: main page, js, images. There are no lags if browser reload simple page. Also, I could not reproduce lags by other network traffic: pings, ssh, scp, downloading files. There are no lags if I compile and so on. Some additional info: The shared irq11 is used by pcm0, em0, iwi0, CardBus, USB, and acpi_video0. [EMAIL PROTECTED]:1:0: class=0x02 card=0x05491014 chip=0x101e8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82540EP Gigabit Ethernet Controller (Mobile)' I just cvsup'ed to the new em 6.7.2 version without FAST interrupt and lags in sound and USB mouse has gone. Thank you. However, if I define EM_FAST_IRQ, then lags appear again. I've just rebuild RELENG_6 with EM_FAST_IRQ enabled and with Scott Long's fix 1.14.2.5 of src/sys/i386/i386/intr_machdep.c and all run without lags. Thank you. em0: Intel(R) PRO/1000 Network Connection Version - 6.7.2 port 0x8000-0x803f mem 0xc022-0xc023,0xc020-0xc020 irq 11 at device 1.0 on pci2 em0: [FAST] -- Igor Sysoev http://sysoev.ru/en/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cryptodev and ssh on RELENG_7
At 03:27 AM 11/27/2007, Harald Schmalzbauer wrote: Hello, I have a HiFN crypto card and can remember that it was used for ssh connections with 3des encryption (on 6.1 afair). But with RELENG_7 it isn't used at all (no interrupts) if I 'ssh -v -c 3des-cbc [EMAIL PROTECTED]' Any ideas what is wrong? dmesg: hifn0 mem 0x8000-0x8fff,0x8004-0x80041fff,0x8008-0x80087fff irq 12 at device 13.0 on pci0 hifn0: [ITHREAD] hifn0: Hifn 7955, rev 0, 32KB dram, pll=0x801ext clk, 4x mult crw-rw-rw- 1 root wheel - 0, 41 Nov 27 08:13:41 2007 /dev/crypto Hi, Are you sure you have device crypto and device cryptodev in the kernel? Also, there is a program in /usr/src/tools/tools/crypto called hifnstats. It will show some usuage stats. e.g. % hifnstats input 43292952 bytes 182393 packets output 43292952 bytes 182393 packets invalid 0 nomem 0 abort 0 noirq 0 unaligned 67775 totbatch 0 maxbatch 0 nomem: map 0 load 0 mbuf 0 mcl 0 cr 0 sd 0 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
connect() returns EADDRINUSE during massive host-host conn rate
Hello, I have a pair of hosts. One of them performs a massive amount of TCP connections to the other one, all to the same port. This setup mostly works fine, but from time to time (that varies, from once a minute to one a half an hour), the connect(2) syscall fails with EADDRINUSE. The connection rate tops to 50 connection initiations/second. The socket is non-blocking. It does standard job of creating the socket, setting up the relevant fields, setting SO_REUSEADDR and SO_KEEPALIVE, setting O_NONBLOCK on the descriptor. No bind(2) is performed. The connection is initiated from inside a jail (not sure if that implies a internal bind(2) to the jail's address). There are no connections from the other host to the first one. I've tried tuning the net.inet.ip.portrange variables: I've increased the available portrange to over 45000 ports (quite a lot, should be more than enough for just anything) and I've toggled net.inet.ip.portrange.randomized off, but that didn't change anything. The workaround on the application side - retrying on EADDRINUSE - works pretty well, but hey, from what I know from the Stevens book, that shouldn't be happening, though Google said all BSD had a bad habit of throwing out EADDRINUSE from time to time. This all happens on a 6.2-RELEASE system. The symptoms are easily reproducable in my environment. Is there any known fix for that? If there ain't, can it be fixed? :) -- Jan Srzednicki :: http://wrzask.pl/ Remember, remember, the fifth of November -- V for Vendetta ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: installation problems of FreeBSD 7 beta 2 on Dell D610 (multiboot con solaris, linux, winxp)
Stefano stable@ I saw similar installing 7.0-BETA3 on my Digital HiHote Ultra ... I'll look for right syntax. eg maybe hw.ata.ata_dma=0 etc starting in my http://www.berklix.com/~jhs/hardware/laptops/#loader.conf Safe mode (Hit Key 3 after it asks for boot floppy 2nd time (Im using floppy as my cd drive doesnt like my cd-rw media, just cd-r) This sets hw.ata.ata_dma to 0, with this my laptop is now in middle of a minimal install, reading distrib via a pcmcia ep0 ethernet. Good luck. -- Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com Ihr Rauch = mein allergischer Kopfschmerz. Dump cigs 4 snuff. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Some processes stay active after killing its PID
On Tue, Nov 27, 2007 at 01:05:21PM +0100, Honza Holakovsky wrote: Thanks for reply, I tried to kill the process via all possibilities described in man kill :) But I didn't know there are some processes which can't be killed, so I tried again running wdfs, but after ps -xacu | grep wdfs I see USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 971 73,9 0,9 19048 5552 ?? Rs1:03od 0:15,36 wdfs no D state :( I'm quite confused, because in state, I have to reboor every time I umount wdfs drive :( By default, the shell uses it's built-in kill function. Try invoking the real kill directly, as root; '/bin/kill -9 971' Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpdJHldKH9Z1.pgp Description: PGP signature
Re: Some processes stay active after killing its PID
Well, didn't know that, /bin/kill -9 wdfs_PID works, great Thanks a lot, after your advice I read an article about csh built-in commands, never heard of it from any fbsd handbook... 2007/11/27, Roland Smith [EMAIL PROTECTED]: On Tue, Nov 27, 2007 at 01:05:21PM +0100, Honza Holakovsky wrote: Thanks for reply, I tried to kill the process via all possibilities described in man kill :) But I didn't know there are some processes which can't be killed, so I tried again running wdfs, but after ps -xacu | grep wdfs I see USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 971 73,9 0,9 19048 5552 ?? Rs1:03od 0:15,36 wdfs no D state :( I'm quite confused, because in state, I have to reboor every time I umount wdfs drive :( By default, the shell uses it's built-in kill function. Try invoking the real kill directly, as root; '/bin/kill -9 971' Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Some processes stay active after killing its PID
On Tue, 27 Nov 2007, Honza Holakovsky wrote: Well, didn't know that, /bin/kill -9 wdfs_PID works, great Thanks a lot, after your advice I read an article about csh built-in commands, never heard of it from any fbsd handbook... I am completely baffled why this worked. Why would /bin/kill -9 work when the built in csh kill -9 wouldn't? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Some processes stay active after killing its PID
On Tue, 27 Nov 2007 20:14:50 +0100 Honza Holakovsky [EMAIL PROTECTED] wrote: Thanks a lot, after your advice I read an article about csh built-in commands, never heard of it from any fbsd handbook... FWIW, the builtin(1) man page has a table which shows the builtin commands for both csh and sh. -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Some processes stay active after killing its PID
On Tue, Nov 27, 2007 at 01:24:56PM -0600, Stephen Montgomery-Smith wrote: On Tue, 27 Nov 2007, Honza Holakovsky wrote: Well, didn't know that, /bin/kill -9 wdfs_PID works, great Thanks a lot, after your advice I read an article about csh built-in commands, never heard of it from any fbsd handbook... I am completely baffled why this worked. Why would /bin/kill -9 work when the built in csh kill -9 wouldn't? According to the manual page for the built-in kill command, it recognizes 'kill -s 9', but not 'kill -9'. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpVAmptlKnGl.pgp Description: PGP signature
Re: Some processes stay active after killing its PID
On Tue, Nov 27, 2007 at 08:59:06PM +0100, Roland Smith wrote:
On Tue, Nov 27, 2007 at 01:24:56PM -0600, Stephen Montgomery-Smith wrote:
On Tue, 27 Nov 2007, Honza Holakovsky wrote:
Well, didn't know that, /bin/kill -9 wdfs_PID works, great
Thanks a lot, after your advice I read an article about csh built-in
commands, never heard of it from any fbsd handbook...
I am completely baffled why this worked. Why would /bin/kill -9 work when
the built in csh kill -9 wouldn't?
According to the manual page for the built-in kill command, it
recognizes 'kill -s 9', but not 'kill -9'.
What's even more awesome is that the csh manpage actually refers to
the use of the kill -[signal] syntax:
or from a command run at completion time:
complete kill 'p/*/`ps | awk \{print\ \$1\}`/'
kill -9 [^D]
23113 23377 23380 23406 23429 23529 23530 PID
Hooray for consistency.
--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Some processes stay active after killing its PID
On Tue, Nov 27, 2007 at 08:59:06PM +0100, Roland Smith wrote: On Tue, Nov 27, 2007 at 01:24:56PM -0600, Stephen Montgomery-Smith wrote: On Tue, 27 Nov 2007, Honza Holakovsky wrote: Well, didn't know that, /bin/kill -9 wdfs_PID works, great Thanks a lot, after your advice I read an article about csh built-in commands, never heard of it from any fbsd handbook... I am completely baffled why this worked. Why would /bin/kill -9 work when the built in csh kill -9 wouldn't? According to the manual page for the built-in kill command, it recognizes 'kill -s 9', but not 'kill -9'. The man page is wrong % xcalc [1] 4730 % kill -BUS 4730 % [1]Bus error xcalc % xcalc [1] 4731 % kill -10 4731 % [1]Bus error xcalc % echo $SHELL /bin/tcsh % LSOF shows I'm using the system tcsh, and AFAIK it behaves the same for being invoked as both /bin/csh and /bin/tcsh Gary ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Some processes stay active after killing its PID
* Roland Smith [EMAIL PROTECTED] [071127 11:59] wrote: On Tue, Nov 27, 2007 at 01:24:56PM -0600, Stephen Montgomery-Smith wrote: On Tue, 27 Nov 2007, Honza Holakovsky wrote: Well, didn't know that, /bin/kill -9 wdfs_PID works, great Thanks a lot, after your advice I read an article about csh built-in commands, never heard of it from any fbsd handbook... I am completely baffled why this worked. Why would /bin/kill -9 work when the built in csh kill -9 wouldn't? According to the manual page for the built-in kill command, it recognizes 'kill -s 9', but not 'kill -9'. Is it too late to remove csh from the base system? :D -- - Alfred Perlstein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: msdosfs performance unbearable
* Dominic Fandrey [EMAIL PROTECTED] [071127 00:47] wrote: ufs: $ time -h tar -xf php_manual_en.tar.gz 3.31s real 0.43s user 0.51s sys msdosfs: I stopped that after 45 minutes. Also the system becomes barely responsive. The mouse moves extremely sloppy and a key-press often causes 2 characters to be printed. Mouse-clicks are either lost or take more than 10 seconds to be recognized. Which version of FreeBSD? can you get more information about the FAT system? -- - Alfred Perlstein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Some processes stay active after killing its PID
On Tue, 27 Nov 2007, Alfred Perlstein wrote: * Roland Smith [EMAIL PROTECTED] [071127 11:59] wrote: On Tue, Nov 27, 2007 at 01:24:56PM -0600, Stephen Montgomery-Smith wrote: On Tue, 27 Nov 2007, Honza Holakovsky wrote: Well, didn't know that, /bin/kill -9 wdfs_PID works, great Thanks a lot, after your advice I read an article about csh built-in commands, never heard of it from any fbsd handbook... I am completely baffled why this worked. Why would /bin/kill -9 work when the built in csh kill -9 wouldn't? According to the manual page for the built-in kill command, it recognizes 'kill -s 9', but not 'kill -9'. Is it too late to remove csh from the base system? :D :) Whatever tcsh(1) may say, kill -9 (aka kill -KILL) has always worked fine in csh here; I've never used kill -s. I'm as baffled as Stephen. paqi% cat - [1] 5186 paqi% kill -9 5186 [1]Killedcat - Sure that's 'overkill', and that said, I've had processes that were unkillable short of rebooting, including an errant mpd4 beta earlier this year, when I certainly did try /bin/kill -9 too. [5.5-STABLE] Cheers, Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6 tinderbox] failure on sparc64/sparc64
TB --- 2007-11-28 03:59:29 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2007-11-28 03:59:29 - starting RELENG_6 tinderbox run for sparc64/sparc64 TB --- 2007-11-28 03:59:29 - cleaning the object tree TB --- 2007-11-28 04:00:00 - cvsupping the source tree TB --- 2007-11-28 04:00:00 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/sparc64/sparc64/supfile TB --- 2007-11-28 04:00:06 - building world (CFLAGS=-O2 -pipe) TB --- 2007-11-28 04:00:06 - cd /src TB --- 2007-11-28 04:00:06 - /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything TB --- 2007-11-28 04:52:43 - generating LINT kernel config TB --- 2007-11-28 04:52:43 - cd /src/sys/sparc64/conf TB --- 2007-11-28 04:52:43 - /usr/bin/make -B LINT TB --- 2007-11-28 04:52:43 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-28 04:52:43 - cd /src TB --- 2007-11-28 04:52:43 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Nov 28 04:52:43 UTC 2007 stage 1: configuring the kernel -- cd /src/sys/sparc64/conf; PATH=/obj/sparc64/src/tmp/legacy/usr/sbin:/obj/sparc64/src/tmp/legacy/usr/bin:/obj/sparc64/src/tmp/legacy/usr/games:/obj/sparc64/src/tmp/usr/sbin:/obj/sparc64/src/tmp/usr/bin:/obj/sparc64/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /obj/sparc64/src/sys/LINT /src/sys/sparc64/conf/LINT config: /src/sys/sparc64/conf/LINT:687: only one machine directive is allowed *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-11-28 04:52:43 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-11-28 04:52:43 - ERROR: failed to build lint kernel TB --- 2007-11-28 04:52:43 - tinderbox aborted TB --- 2552.06 user 313.46 system 3194.14 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-sparc64-sparc64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
