search for: idendifi

I''ve idendified the problem... description: problem in XEN bridged-network. Dom0 doesn''t respond at external network activity (DomUs may work correctly) problem: something related to Broadcom NetXtreme II menagement solution: follow all this instructions: http://article.gmane.org/gmane.linux.hardwa...

Hello. I'm facing an seemingly unsolvable problem on the Samba servers I administer (on Debian stable). Those servers are registered on a AD domain. They only serve files and are not registered as domain controllers. For some idendified users (always the same), Winbind periodically (but unpredicably) becomes unable to resolve their names, making their shares unavailable. A "net cache flush" temporarily solves the problem. Purging all caches doesn't help. Removing then adding again the servers on the domain doesn...

...n-Pierre Perrin via samba wrote: > Hello. > > > I'm facing an seemingly unsolvable problem on the Samba servers I > administer (on Debian stable). Those servers are registered on a > AD domain. They only serve files and are not registered as domain > controllers. For some idendified users (always the same), Winbind > periodically (but unpredicably) becomes unable to resolve their names, > making their shares unavailable. A "net cache flush" temporarily > solves the problem. Purging all caches doesn't help. Removing then > adding again the servers on...

...orted yesterday. I have a 3 factors (2x3x2) dataset that I collapsed into a 2 factors dataset (3x2 = sizexModality). For size==small, I have 2 observations per subject (Snr), for the other sizes only 1. I reckoned that aov (and underneath, lm) might handle this as it should, since the subjects are idendified, when I do > aov( y~Modality*size + Error(Snr/(Modality*size)) ) I indeed get a result without any warning. Remembering a remark on unbalanced designs in aov, I ran the same (?..) test in NCSS. It too gives results without any warnings or errors, but they're not exactly the same. The DF,...

...quiring kexec-tools to manually merge resources when creating a kdump header. The current kexec-tools resource count limit does not allow more than ~100GB of memory with a memory block size of 128MB on x86-64). Let's allow to selectively merge resources, speciyfing a parent node and a resource idendifier string. The memory unplug path will properly split up merged resources again. Patch #3 contains a /proc/iomem example. Only tested with virtio-mem. Note: This gets the job done and is comparably simple. More complicated approaches would require introducing IORESOURCE_MERGEABLE and extending our...