search for: unallow

zfs receive should allow option to disable immediately mount of received filesystem. In case of original filesystem have changed mountpoints, it''s hard to make clone fs with send-receive, because received filesystem immediately try to mount to old mountpoint, that locked by sourcr fs. In case of different host mountpoint can be locked by unrelated filesystem. Can anybody recommend a

...ow... my question: Why? What does the W2K client do that triggers this barrage of rejected authentications of a user 'nobody' (that is clearly not allowed to enter)? More importantly, is there a way to configure EITHER the W2K client or the Samba server (or both) to not waste time on these unallowed accesses? Since smbclient produces such a clean entry, I would assume the fix must be on the client side (W2K) only. But I would take any advice. :) Thanks in advance, Lynn (Samba 2.2.8a on AIX 5.1) __________________________________ Do you Yahoo!? Yahoo! Search - Find what you’re looking for...

Hello, Are there any 'unallowed' (meta)characters that can cause R to parse a file incorrectly when using read.table? --Dawn Here the background if it's needed: I'm new to R, but have done some Perl. I'm trying to read in a data.frame from a file using * as a record separator. data <- read.table(&quo...

...th nesting support. My current plan is to implement an IST handler which switches itself off the IST stack as soon as possible, freeing it for re-use. The flow would be roughly like this upon entering the handler; build_pt_regs(); RSP = pt_regs->sp; if (RSP in VC_IST_stack) error("unallowed nesting") if (RSP in current_kernel_stack) RSP = round_down_to_8(RSP) else RSP = current_top_of_stack() // non-ist kernel stack copy_pt_regs(pt_regs, RSP); switch_stack_to(RSP); To make this NMI safe, the NMI handler needs some logic too. Upon entering NMI, it needs to check the r...

...ow... my question: Why? What does the W2K client do that triggers this barrage of rejected authentications of a user 'nobody' (that is clearly not allowed to enter)? More importantly, is there a way to configure EITHER the W2K client or the Samba server (or both) to not waste time on these unallowed accesses? Since smbclient produces such a clean entry, I would assume the fix must be on the client side (W2K) only. But I would take any advice. :) Please note that I am not allowed (in my corporate environment) to enable the guest account on this machine. Therefore, the solution must not invo...

Hi, we are using centos 7 as an nfs-server. Chown / chmod on all linux clients (RH5,6, Ubuntu 14.04) don't get any errors from unallowed chown/chmod commands. Return-code is 0. e.g. ls -al test.txt -rwxrwxr-x 1 sanderso users 0 26. Jan 15:09 test.txt chown otheruser test.txt echo $? 0 ls -al test.txt -rwxrwxr-x 1 sanderso users 0 26. Jan 15:09 test.txt last posting here describes the error. http://webcache.googleusercontent.com/...

Hi all, I have looked a bit at what it would take to make the SYSLINUX current directory settable when loading a new configuration file with the CONFIG directive. I have come to the conclusion that it would be a lot less invasive to simply maintain the rule that the current working directory is the one where the config file lives, *including* one loaded via the CONFIG directive. The obvious

...same machine, connect sshd by ssh ssh -c 3des-cbc localhost ssh -c aes128-cbc localhost ssh -c aes192-cbc localhost ssh -c aes256-cbc localhost These above ciphers are FIPS allowed and ssh can successfully connect to sshd which is running in FIPS mode. On the other hand,when using FIPS unallowed ciphers, ssh -c arcfour localhost ssh -c blowfish-cbc localhost ssh -c cast128-cbc locahost the sshd will disconnect the connection. Some debug messages like below appear. *************************** debug2: set_newkeys: mode 1 cipher_init: EVP_CipherInit: set key failed for aes128-ct...

Hi, What does this message imply? [Apr 29 14:46:30] NOTICE[32175] channel.c: Dropping incompatible voice frame on IAX2/trunk1-9085 of format alaw since our native format has changed to 0x4 (ulaw) If voice frames have been dropped then I suppose that the call quality may be affected? Vieri

...nt an IST handler which switches itself off > the IST stack as soon as possible, freeing it for re-use. > > The flow would be roughly like this upon entering the handler; > > build_pt_regs(); > > RSP = pt_regs->sp; > > if (RSP in VC_IST_stack) > error("unallowed nesting") > > if (RSP in current_kernel_stack) > RSP = round_down_to_8(RSP) > else > RSP = current_top_of_stack() // non-ist kernel stack > > copy_pt_regs(pt_regs, RSP); > switch_stack_to(RSP); > > To make this NMI safe, the NMI handler needs some log...

...ou mean 32-bit? 64-bit kernels have exactly the same problem. At least the stack is okay, though. Anyway, since I'm way behind on this thread, here are some thoughts: First, I plan to implement actual precise recursion detection for the IST stacks. We'll be able to reliably panic when unallowed recursion happens. Second, I don't object *that* strongly to switching to a second #VC stack if an NMI or MCE happens, but we really need to make sure we cover *all* the bases. And #VC is distressingly close to "happens at all kinds of unfortunate times and the guest doesn't actual...

On 23/06/2020 14:03, Peter Zijlstra wrote: > On Tue, Jun 23, 2020 at 02:12:37PM +0200, Joerg Roedel wrote: >> On Tue, Jun 23, 2020 at 01:50:14PM +0200, Peter Zijlstra wrote: >>> If SNP is the sole reason #VC needs to be IST, then I'd strongly urge >>> you to only make it IST if/when you try and make SNP happen, not before. >> It is not the only reason, when ES

On Sat, Apr 25, 2020 at 1:23 PM Joerg Roedel <joro at 8bytes.org> wrote: > > On Sat, Apr 25, 2020 at 12:47:31PM -0700, Andy Lutomirski wrote: > > I assume the race you mean is: > > > > #VC > > Immediate NMI before IST gets shifted > > #VC > > > > Kaboom. > > > > How are you dealing with this? Ultimately, I think that NMI will need

ZFS introduces a new and incompatible ACL interface into Solaris and this seems to be not yet fully completed in addition to the fact that is causes a lot of problems for software that needs to be compatible with Solaris-2.5 like star. Proof for incompatibility: create a file on UFS and set an ACL for this file. Use Sun tar cpf out file to archive this file. Unpack this archive file on ZFS