search for: hinky

AdvisoRs: Is the following a bug, feature, hinky error message, or dumb Bert? > mtest <- matrix(1:12,nr=4) > dftest <- data.frame(mtest) > ix <- cbind(1:2,2:3) > mtest[ix] <- NA > mtest [,1] [,2] [,3] [1,] 1 NA 9 [2,] 2 6 NA [3,] 3 7 11 [4,] 4 8 12 ## But ... > dftest[ix] <-...

...sure if replication is actually working or not. Here's what I get from ./samba-tool drs showrepl I've also done. [./samba-tool drs kcc -Uadministrator dc2.samba.somedom.local] in an attempt to fix the replication problem. (or what I think is a problem.) [The outbound neighbors data seems hinky... and searches on similar cases don't seem to return much useful data.] --- Default-First-Site-Name\DC1 DSA Options: 0x00000001 DSA object GUID: b895f491-759f-4c72-a068-d1a40d0a8f4a DSA invocationId: e72417ee-e57b-430f-b636-1d3745a94c89 ==== INBOUND NEIGHBORS ==== DC=ForestDnsZones,DC=samba...

...ssfully modify/add files in their home directory, in /tmp/, as necessary. As long as it is on local file storage... This system NFS mounts the remote file storage resource on a backend RHEL4 server. The public facing web frontends also mount these same resources. Here is where things get hinky -- some users can write to the directories on the NFS mount, and some cannot. If the directory in question is owned by the user, then no problems writing. If not, but the directory's owning group contains the user as a member, then only sometimes can the user add/change/remove files in...

...boxes to a laptop. > > when I do this, I really do want to zero/delete the file > afterward. > > I use rsync because its a lowest common denominator, and its fast > and reliable. > > But, I have to zero the maildrop afterward. This I do via a script > but it feels very hinky, much less atomic to having the daemon > do it. > > None of the --delete-variant seem to work as a pass to the OTHER end > so the pullee can say :"after you give me this, delete it" > > Is it done/doable? I think what you want is the proposed --move option, which woul...

I am using Samba for print serving on a home network that consists of one Win98 machine and one running Red Hat 6. I am getting along well but have come up against a problem I don't know how to solve. On the linux machine where samba is running, when I am in a text based terminal (doesn't show in KDE) I get various nmbd messages scrolling across my screen, messages that look like nmbd

...oogle/RTFM as well as reading the pam documentation on the CentOS client machine, and don't find anything that helps me figure out is causing it to think the account has expired. The LDAP attributes that I think are relevant on a test account are below. I don't see anything here that looks hinky, but then I am fairly ignorant on PAM authentication. shadowExpire 0 shadowFlag 0 shadowInactive 0 shadowLastChange 14816 shadowMax 99999 shadowMin 0 shadowWarning 7 Bill -- INTERNET: bill at celestial.com Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641...

...arious reasons > may be undesirable. > > Do you have a feel for the complexity involved with the ARM code? What > were the troublesome parts and corner cases, etc.? The register scavenger depends on correct kill flags after register allocation. It will assert if it detects something hinky. Adding scavenger support to the x86 PEI is fairly simple. Fixing the many scavenger assertions that follow is not. The fundamental problem is that currently nothing in the x86 target depends on correct liveness after register allocation. Since many post-RA passes modify the code, there is a good...

Jakob Stoklund Olesen <stoklund at 2pi.dk> writes: Hi Jakob, Thanks for the responses. > As you have noticed, the x86 backend only supports stack frames up to 2GB. That's unfortunate. :( > Fixing that would require the x86 backend to use the register > scavenger during prolog epilog insertion like the ARM backend does. Makes sense. > That particular code was very

...given that this has turned into a balloon-squeezing exercise, I want to make sure I'm not doing this the wrong way. What is the currently accepted best method for fixing this? And given that this happened on a nearly brand-new deployment, it worries me a bit that this happened while nothing hinky was going on - I installed Gluster manually, but the rest of the systems management has been via Ovirt. Has anyone else seen issues with this? Thanks, -j - - snip - - [2018-03-06 00:14:06.141281] I [MSGID: 106490] [glusterd-handler.c:2891:__glusterd_handle_probe_query] 0-glusterd: Received pro...

I''m attempting to wrestle an old DB into Rails. This relationship is giving me trouble: class Show < AR::Base has_many :segments end class Segment < AR::Base belongs_to :show has_one :media #this has no PK/FK relation end A Segment is "linked" to Media by Media.name, which is the result of concatenating Segment.name and Segment.part. As I said there are is no

...e>/ from the good node to the rejected one and restart glusterd service on the rejected peer. > > What is the currently accepted best method for fixing this? > > And given that this happened on a nearly brand-new deployment, it worries > me a bit that this happened while nothing hinky was going on - I installed > Gluster manually, but the rest of the systems management has been via > Ovirt. Has anyone else seen issues with this? > > Thanks, > > -j > > > > [2018-03-06 00:14:06.141281] I [MSGID: 106490] [glusterd-handler.c:2891:__glusterd_handle_probe...

My code was hinky, but only in the sense that I was accidentally duplicating the definition variable in the module where the function was. With only the declaration in the second module loading the bitcode reproduces the issue. Managed an lli reproduction: $ cat jit-0.ll target datalayout = "e-m:x-p:32:32-i64...

That's useful to know that the static compilation code path works. Furthermore, as expected from that: 52: c7 05 04 00 00 00 d5 00 00 00 movl $213, 4 00000054: IMAGE_REL_I386_DIR32 _foo It looks like the offset `4` of the second field of your struct is correct in the object file, so this does seem to be a problem in the JIT-specific linking/loading.

Hi All, I have what I think is a ZFS related bug. Unfortunately my simplest test case is a bit cumbersome and I haven't definitively proven that the problem is ZFS related. I'm hoping for some feedback on how to move forward. Quick background: I rip my CD's using grip and produce flac files. I tag the music using Musicbrainz' Picard and transcode it to mp3's within Picard

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21-rc7 + your patches + the last batch of pv_ops patches I posted. This patch generally restricts itself to Xen-specific parts of the tree, though it does make a few small changes elsewhere. These patches include: - some helper routines for allocating address space and walking pagetables - Xen

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21-rc7 + your patches + the last batch of pv_ops patches I posted. This patch generally restricts itself to Xen-specific parts of the tree, though it does make a few small changes elsewhere. These patches include: - some helper routines for allocating address space and walking pagetables - Xen

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21-git3 + ff patches-2.6.21-git3-070501-1.tar.gz. Changes since the last posting: - reviews of xenbus (me), netfront (hch, rusty, herbert xu) and blockfront (hch), with most comments addressed. Netfront review revealed a couple of real bugs, and the code for all three is looking cleaner

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21-git3 + ff patches-2.6.21-git3-070501-1.tar.gz. Changes since the last posting: - reviews of xenbus (me), netfront (hch, rusty, herbert xu) and blockfront (hch), with most comments addressed. Netfront review revealed a couple of real bugs, and the code for all three is looking cleaner

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21 + 2.6.21-070428-1 + the patches I've posted over the last couple of days. Changes since the last posting: - update per review comments - comment each file - comment barrier use - use common cpu sibling setup - fixed a few minor bugs, specifically a traceirq mismatch warning - some

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21 + 2.6.21-070428-1 + the patches I've posted over the last couple of days. Changes since the last posting: - update per review comments - comment each file - comment barrier use - use common cpu sibling setup - fixed a few minor bugs, specifically a traceirq mismatch warning - some