search for: 12342

...16784 16729 16596 16595 16591 16584 16563 16440 16414 16191 16088 16077 16058 16052 16046 16045 15957 15931 15885 15867 15799 15782 15704 15222 15221 15197 15100 15008 14918 14915 14788 14755 14518 14492 14398 14284 14273 14272 14173 13824 13501 13346 13255 13252 13166 13022 12899 12820 12597 12583 12342 12332 11683 11600 11546 11371 11301 11297 11267 11256 11191 10907 10800 10090 10086 10023 9924 9868 9758 9731 9273 9205 9182 9126 9090 8876 8465 8155 8042 8026 7908 7809 7711 7691 7464 7447 6691 6689 6596 6585 6462 6419 6407 5949 5937 5934 5927 5808 5729 5644 5643 5558 5521 5425 5309 5226 5182 5181...

Over the past 2 days, my smbd processes are multiplying worse than rabbits. At least with rabbits it's easy to tell why you wind up with so many... Here's the setup: Samba version 3.2.8-0.24 installed via rpm on a FC6 box with 2 nics, both on the same subnet. The samba server acts as a PDC in a mixed environment but mostly windows pc's running xp. It is used mostly for file

when I load my data file in txt format into the R workstation I lose about 6000 rows, this is a problem. Is there a limit to the display capabilities for the workstation? is all the information there and I just can't see the first couple thousand rows? -- View this message in context: http://www.nabble.com/txt-file%2C-14000%2B-rows%2C-only-last-8000-appear-tp17701519p17701519.html Sent from

Hello, I am working on creating a simple interface for an ldap user repository. A little background, for development, I am working under Cygwin, with an ssh port forward on port 636 (for SSL). I have included clips of my error message and all config/environment/model files below. I replaced domain information, which I have double checked with "<CORRECT>". Please let me know

Configuration: Linux wpbx 2.4.9-13 #1 Tue Oct 30 20:11:04 EST 2001 i686 unknown P4 2.5 GHz, 1 GB RAM T400P with 3 T1s plugged in. A flow of 46 calls (spread out over 3 T1s). Each call gets transferred (Dial) to the SIP platform and stays for 5 min. Case 1. Asterisk built out of CVS Mar. 19. Test was running for 3 days. Segmentation fault. Case 2. Asterisk built out of CVS Apr. 1. Test was running

...chan_zap.c: Ignore switch to REVERSED Polarity on channel 1, state 6 [Mar 16 10:57:21] DEBUG[12331] chan_zap.c: Ignore switch to REVERSED Polarity on channel 1, state 6 [Mar 16 10:58:57] DEBUG[12338] chan_zap.c: Ignore switch to REVERSED Polarity on channel 1, state 6 [Mar 16 10:59:43] DEBUG[12342] chan_zap.c: Ignore switch to REVERSED Polarity on channel 1, state 6 [Mar 16 11:01:34] DEBUG[12355] chan_zap.c: Ignore switch to REVERSED Polarity on channel 1, state 6 [Mar 16 11:02:27] DEBUG[12360] chan_zap.c: Ignore switch to REVERSED Polarity on channel 3, state 6 [Mar 16 11:02:50] DEBUG...

...e: 128, 0, 0, 0, 0 FFS inode: 132, 0, 484, 67, 498 SWAPMETA: 276, 121576, 0, 0, 0 rtentry: 132, 0, 13, 74, 14 unpcb: 140, 25620, 14, 70, 39 ripcb: 180, 12342, 0, 0, 0 sackhole: 20, 0, 0, 0, 0 tcpreass: 20, 1690, 0, 0, 0 hostcache: 76, 15400, 0, 0, 0 syncache: 100, 15366, 0, 0, 0 tcptw: 48, 2496, 0,...

Hi: I''ve met an ext4 Bug in dom0 kernel 2.6.32.36. (See kernel stack below) 32.36 kernel commit: http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=ae333e97552c81ab10395ad1ffc6d6daaadb144a The bug only show up in our cluster environments which includes 300 physical machines, one server will run into this bug per day. Running ontop of every server, there are about 30