search for: 44kb

...amba PDC during an attempted machine password change. I tried posting it as an attachment, but I guess the list won't accept that. I would be happy to e-mail it to a developer or anyone else who is willing to have a look and see if the explanation to the problem is in there. The file is only 44Kb, or 24 Kb when zipped. Here is a repost of my original message: None of the Win 2000 workstations on my Samba 3.02 network is able to change its password. Every machine's event log contains error messages every 30 days like this: Changing machine account password for account P2450-2$ faile...

...me fix this problem, that would do the trick too. Best, Kasper ---------------- trying URL 'http://www.sourcekeg.co.uk/cran/src/contrib/tensorA_0.31.tar.gz' Content type 'application/x-tar' length 45248 bytes opened URL ================================================== downloaded 44Kb * Installing *source* package 'tensorA' ... ** libs gcc -I/usr/lib/R/include -fPIC -g -O2 -c tensora.c -o tensora.o gcc -shared -o tensorA.so tensora.o -L/usr/lib/R/lib -lR ** R ** preparing package for lazy loading Error in gettext(domain, unlist(args)) : invalid 'domain'...

...@{path to a response file} I then receive an error message: clang++: error: unable to execute command: Couldn't execute program '(path to ld.lld)': The filename or extension is too long. If I then rerun clang++ with -v, I get the full command line passed to lld (which is approximately 44KB). It looks like there was previously a patch that tried to address this issue for certain platforms ( https://reviews.llvm.org/rL334295) but this doesn't seem to have fixed the issue in my case. Is there some way to work around this issue? Since the decision of whether to use a response file o...

...40] DMA free:15764kB min:28kB low:32kB high:40kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB managed:15908kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:44kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes [584564.942442] lowmem_reserve[]: 0 2980 3940 3940 [584564.942456] DMA32 free:9868kB min:6060kB low:7572kB high:9088kB active_anon:2367984kB inactive_anon:592000kB active_fi...

...:27715 inactive_file:277856 isolated_file:0 [488054.896499] unevictable:0 dirty:30010 writeback:0 unstable:0 [488054.896501] free:2220 slab_reclaimable:11510 slab_unreclaimable:1813 [488054.896503] mapped:2981 shmem:102 pagetables:1274 bounce:0 [488054.896532] Node 0 DMA free:6996kB min:36kB low:44kB high:52kB active_anon:0kB inactive_anon:152kB active_file:56kB inactive_file:5148kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:12304kB mlocked:0kB dirty:0kB writeback:0kB mapped:32kB shmem:0kB slab_reclaimable:100kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:...

...see it immediately overwritten. For example: $ scp amsterdam:*.c /tmp/a ether82557.c 100% 29KB 29.4KB/s 00:00 sdaoe.c 100% 16KB 15.8KB/s 00:01 sdaow.c 100% 44KB 44.1KB/s 00:00 serial.c 100% 1480 1.5KB/s 00:00 x.c 100% 220 0.2KB/s 00:00 $ ls -l /tmp/a -rw-rw-r-- 1 rsc rsc 220 2005-09-24 22:14 /tmp/a $ Russ Cox rsc at swtch.com -...

...of floor * residue on the fly or you need twice as much. 3) Window shapes need to be somewhat precalculated. Size depends on how much you mind approximation and playing tricks with table lookups. For an 8192 point window, I'd say 8KB is a reasonable ball park figure. That's already about 44KB. Given a processor like a Cirrus 7312 (very common), which has 48KB of internal SRAM, you'd be hard pressed to fit everything given a worst case in-spec file. It would spill to SDRAM and you'd suffer a large performance hit all of a sudden. That's assuming your processor even has SDRAM....

CentOS 6.3, x86_64. I have noticed when building a new software RAID-6 array on CentOS 6.3 that the mismatch_cnt grows monotonically while the array is building: # cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] md11 : active raid6 sdg[5] sdf[4] sde[3] sdd[2] sdc[1] sdb[0] 3904890880 blocks super 1.2 level 6, 512k chunk, algorithm 2 [6/6] [UUUUUU]

On Tue, Jan 26, 2016 at 1:51 PM, Michal Privoznik <mprivozn@redhat.com> wrote: > On 26.01.2016 14:35, Andrei Perietanu wrote: > > On Tue, Jan 26, 2016 at 12:39 PM, Michal Privoznik <mprivozn@redhat.com> > > wrote: > > > >> On 26.01.2016 12:30, Andrei Perietanu wrote: > >>> Hi all, > >>> > >>> I am running KVM on a 3.18

Hi there, I've been trying to mount my NTFS partitions with the NTFS-3g project's FUSE implementation but am unable to mount anything. I'm on 6-STABLE and have the latest versions of FUSE installed: fusefs-kmod-0.3.0_4 Kernel module for fuse fusefs-libs-2.6.2 FUSE allows filesystem implementation in userspace fusefs-ntfs-0.20070207RC1 Mount NTFS partitions and disk images I use

...71] free:6911872 slab_reclaimable:29430 slab_unreclaimable:34726 Dec 27 09:19:05 2013 kernel: : [277622.359371] mapped:45784 shmem:9850 pagetables:107714 bounce:0 Dec 27 09:19:05 2013 kernel: : [277622.359371] free_cma:0 Dec 27 09:19:05 2013 kernel: : [277622.359382] DMA free:2332kB min:36kB low:44kB high:52kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15968kB managed:6960kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:8kB slab_unreclaimable:288kB kernel_stack:0kB pagetables:0kB u...

branch xen-unstable xen branch xen-unstable job test-amd64-i386-rhel6hvm-amd test redhat-install Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git Tree: xen http://xenbits.xen.org/staging/xen-unstable.hg *** Found and reproduced problem

...3.10 branch. Sorry for being so late with this. <blurb> It has the ''feature-max-indirect-segments'' implemented in both backend and frontend. The current problem with the backend and frontend is that the segment size is limited to 11 pages. It means we can at most squeeze in 44kB per request. The ring can hold 32 (next power of two below 36) requests, meaning we can do 1.4M of outstanding requests. Nowadays that is not enough. The problem in the past was addressed in two ways - but neither one went upstream. The first solution to this proposed by Justin from Spectralogic w...