search for: unpleasant

I've run into an unpleasant oddity involving the interaction of environments and generic functions. I want to check my diagnosis, and see if there is a good way to avoid the problem. Problem: A library defines "foo" <- function(object) 1 setMethod("foo", c("matrix"), function(object) 30) Af...

There is a conflict in glibc between <linux/in.h> and <netinet/in.h>: one defines protocols with an enum, the other does the same, but adds a self-define for every enumerated value. #define IPPROTO_IP IPPROTO_IP This means the two cannot be mixed, and since loads of include files refer to <netinet/in.h>, effectively <linux/in.h> cannot be used with glibc. Since

...hough so I > prefer that to a "warn and ignore" behaviour: > > data.frame(a = 1, b = 2, 3) > > #> a b X3 > > #> 1 1 2 3 > > > data.frame(a = 1, 2, 3) > > #> a X2 X3 > > #> 1 1 2 3 > > > (and in general warnings make for unpleasant debugging so I prefer when we > don't add new ones if avoidable) > I find silence to be much more unpleasant in practice when debugging, myself, but that may be a personal preference. > > > playing a bit more with it, it would make sense to me that the following > have the...

...>> >> #> a b X3 >> >> #> 1 1 2 3 >> >> >> data.frame(a = 1, 2, 3) >> >> #> a X2 X3 >> >> #> 1 1 2 3 >> >> >> (and in general warnings make for unpleasant debugging so >> I prefer when we don't add new ones if avoidable) >> > I find silence to be much more unpleasant in practice when > debugging, myself, but that may be a personal preference. +1 I also *strongly* disagree with the claim " in general...

This patch adds a facility to block on a particular event channel, for when a domain needs to block, but cannot enable interrupts. A domain uses the call something like this: while (1) { clear_evtchn_pending(evtchn); if (check_for_data(evtchn)) break; HYPERVISOR_block_on(evtchn); } The clear of the pending is needed to ensure that any subsequent calls to block_on() don''t

...>> >> #> a b X3 >> >> #> 1 1 2 3 >> >> >> data.frame(a = 1, 2, 3) >> >> #> a X2 X3 >> >> #> 1 1 2 3 >> >> >> (and in general warnings make for unpleasant debugging so >> I prefer when we don't add new ones if avoidable) >> > I find silence to be much more unpleasant in practice when > debugging, myself, but that may be a personal preference. +1 I also *strongly* disagree with the claim " in general...

...LDAPAdmin, ldap tools etc, when I know OpenLDAP "root" dn and password? Is there such "root" user for Samba AD LDAP?    We have a lot of scripts based on "ldapsearch" (without authentification) and "ldapmodify" (with ldap authentification). It would be very unpleasant if we can not use the scripts with SambaAD.  Thanks, Michal  

I just tried to update a bugzilla PR, and got the following unpleasant message: > Insufficient disk space; try again later Insufficient disk space; > try again later returntosender: cannot select queue for bugzilla- > daemon Insufficient disk space; try again later returntosender: > cannot select queue for postmaster putbody: write error: No space...

Due to unpleasant (but arguably valid) policy changes at work, any SSH server within the work firewall must accept only PKI authentication. Unless we can convince the higher-ups otherwise, we will also have to use the commercial SSH server within the firewall. Of course, I should be able to use whatever client I lik...

...e a way that Samba can use this setup to perform user authentication. I only want to access the shares of the Samba server from about 8 Windows computers. I am aware that I cannot make an Active Directory out of this. At the moment I have stored the users in a local passdb, which works but is very unpleasant. Many thanks and many greetings Thorsten

Hi all, I just had a rather unpleasant experience. After considerable work I finally got a script working and set it to run. It had some memory allocation problems when I came back so I used Windows to stop it. During that process it told me that the script had been changed and asked if I wanted to save it. Not being positive that I&...

...me3 was in RHEL 7.0? It was unstable > and insecure, certainly when used with nvidia drivers. I can't see > how you could justify the effort it would have required to > effectively support an unsupported version of Gnome3, and backporting > I think would have been more than deeply unpleasant. Or they could simply have gone with KDE 4, a stable and mature desktop at the time RHEL 7.0 was out. And not an abomination that had to be potty-trained from scratch again while steadily losing features every other minor upgrade. Niki -- Microlinux - Solutions informatiques durables 7, place d...

...accumulated in a bunch of time-and-date-based files. /some/path/2005-01-02-00-00-02 etc. The best 'read all these files' method I've seen in the r-help archives comes down to for (df in my_list_of_filenames ) { dat <- rbind(dat,my_read_function(df)) } which, unpleasantly, is O(N^2) w.r.t. the number of files. I'm fiddling with other idioms to accomplish the same goal. Best I've come up with so far, after extensive reference to the mailing list archives, is my_read_function.many<-function(filenames) { filenames <- filenames[file.exists(file...

...e: > On Tue, Aug 26, 2014 at 10:16 PM, Andy Lutomirski <luto at amacapital.net> wrote: > > There are two outstanding issues. virtio_net warns if DMA debugging > > is on because it does DMA from the stack. (The warning is correct.) > > This also is likely to do something unpleasant to s390. > > (Maintainers are cc'd -- I don't know what to do about it.) > > This changes the semantics of vring and breaks existing guests when > bus address != physical address. Isn't that what this is suppose to fix? Right now the semantics of the vring is that bus a...

...e: > On Tue, Aug 26, 2014 at 10:16 PM, Andy Lutomirski <luto at amacapital.net> wrote: > > There are two outstanding issues. virtio_net warns if DMA debugging > > is on because it does DMA from the stack. (The warning is correct.) > > This also is likely to do something unpleasant to s390. > > (Maintainers are cc'd -- I don't know what to do about it.) > > This changes the semantics of vring and breaks existing guests when > bus address != physical address. Isn't that what this is suppose to fix? Right now the semantics of the vring is that bus a...

...1] <- NA) : missing value where logical needed MatCor is the following Matrix > MatCor [,1] [,2] [,3] [1,] NA 0.9870676 0.04648933 [2,] 0.98706757 1.0000000 -0.17353590 [3,] 0.04648933 -0.1735359 1.00000000 Do you know why I get such an unpleasant message from so polite a software? Thanks to anybody who could help. ************************************************************************* Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinata...

...aves now (when it doesn't ignore) is more consistent with data.frame() though so I prefer that to a "warn and ignore" behaviour: data.frame(a = 1, b = 2, 3) #> a b X3 #> 1 1 2 3 data.frame(a = 1, 2, 3) #> a X2 X3 #> 1 1 2 3 (and in general warnings make for unpleasant debugging so I prefer when we don't add new ones if avoidable) playing a bit more with it, it would make sense to me that the following have the same output: coefficient <- 3 data.frame(value1 = 5) |> transform(coefficient, value2 = coefficient * value1) #> value1 X3 value2 #...

...authentication. I only want >> to access the shares of the Samba server from about 8 Windows >> computers. I am aware that I cannot make an Active Directory out of >> this. >> >> At the moment I have stored the users in a local passdb, which works >> but is very unpleasant. >> > > That is why Microsoft came up with domains ;-) > > If you look at Active Directory, it is basically composed of kerberos, > ldap and dns., so you can replace your kerberos and ldap servers with a > Samba AD DC, this also come with winbind which will replace sssd. &...

OK... maybe I got a little anxious and ran out and bought a Tyan GX28 with dual Opteron (dual core) processors. (It is a nice server ;) ) I did neglect to find out that you can not manually set the IRQ's on this motherboard. I am now stuck sharing an IRQ with the ethernet controller and no foreseeable end to my dilemma. I have a Digium TE210P and zttest consistently runs at 99.97% which

...ind any commit in the repository addressing such issues). I will try and search for the culprit of the inline assembly and replace it with btsl. As for the issue at hand, although after carefully reading both the thread and re-reading the sections from the instructions set reference it is a rather unpleasant behavior, the error thrown by the toolchain. Since Intel is nowadays by far the biggest vendor for x86/x86_64 hardware and they do not mention a single thing about the existence of suffixes for this instruction, it could be accommodated (maybe with a warning though) and take the second option from...