search for: vagari

...l scripts simply do not work with the 'add user script' setting or if they do, then there is an an undocumented bug, issue, etc. The scripts work fine from the command line but aparently samba won't execute them properly. Since I cannot expect my users to understand enough of the vagaries of Unix to log in with ssh and add thier machines to the system I don't see how samba-ldap can be implemented in a production environment.

I won't add to the quite long discussion about the vagaries of nlminb, but will note that over a long period of software work in this optimization area I've found a number of programs and packages that do strange things when the objective is a function of a single parameter. Some methods quite explicitly throw an error when n<2. It seems nlminb...

All-- I'm attempting to implement something I've wanted for a while...a stdio link to a TCP port forward, at least for SSH2, but preferably for either protocol. There's certainly no technical reason this can't be done, but the vagaries of terminal / file descriptor handling are posing something of a challenge. Does anyone have any suggestions for "correct" approaches for this? I absolutely don't want to simply fork off a version of SSH in the background and connect() to its port forward -- that's quit...

...f so, remove > > all host keys, let sshd create new ones. > > Strictly speaking, *if* you have an interest to make sure that *every* > VM gets unique host keypairs, then you should implement a cleanup > routine that takes care of "everything"? that matters to you. These vagaries are why many environments simply disable the validation of hostkeys in their .ssh/config settings and move on to work that is of some more effective use to their workplace. I've encountered, several times, when sites relied on extensive use of SSH key managed git access and shattered their de...

...host keys, let sshd create new ones. >> >> Strictly speaking, *if* you have an interest to make sure that *every* >> VM gets unique host keypairs, then you should implement a cleanup >> routine that takes care of "everything"? that matters to you. > > These vagaries are why many environments simply disable the validation > of hostkeys in their .ssh/config settings and move on to work that is > of some more effective use to their workplace. I've encountered, > several times, when sites relied on extensive use of SSH key managed > git access an...

...breaks in univesal binaries. The problem is that I > detect cpu features other than just endian-ness at configure time; > things that cannot be detected purely from compiler flags. > > See: > http://www.mega-nerd.com/libsndfile/FAQ.html#Q018 Can you elaborate on what kind of CPU vagaries come into play besides endianess? Do they affect all code or just highly-optimized code? I have built several open source projects as universal binaries and they basically function. If you know of specific risks to look out for, your experiences would help a lot of people. > However, my bigge...

...ew ones. > >> > >> Strictly speaking, *if* you have an interest to make sure that *every* > >> VM gets unique host keypairs, then you should implement a cleanup > >> routine that takes care of "everything"? that matters to you. > > > > These vagaries are why many environments simply disable the validation > > of hostkeys in their .ssh/config settings and move on to work that is > > of some more effective use to their workplace. I've encountered, > > several times, when sites relied on extensive use of SSH key managed &gt...

...s I don't think FileManager is the right API layer to abstract at (it is too specific to Clang's usage, and too hard to propagate through the rest of LLVM). My intuition is that it is better to set out to define a lower level VFS layer that is rich enough to support everything we do and the vagaries of Win32/Unix, but is otherwise minimal. One requirement I hope any proposed VFS design will support is emulating Win32 on Unix (and vice versa), which imposes assorted API complications but I think is worth it overall. I see many positive future technologies we could build if we had a good VFS...

I am attempting to join a windows 7 computer running in virtual box to a samba4 domain (version 4.1.0pre1-GIT-243278a). I get prompted for credentials, I use the provisioned Administrator account, and then get the following: The Following error occured attempting to join the domain "ad.redacted.com" The network path was not found. (I have replaced the actual domain with redacted for

Peter Grayson wrote: > Can you elaborate on what kind of CPU vagaries come into play besides > endianess? One issue I found was the cpu behaviour when converting from float/double to int32 when the source float is outside the range of values that can be represented by the int32. For instance: float int32_ppc in32_x86 2147483649.0...

On 2/7/08, Ralph Giles <ralph.giles@artifex.com> wrote: > And theora, remember. Actually, I thought I remember derf doing that. And there it was on Trac's timeline. Look at changeset 14369: "Copy the libogg bitpacker directly into libtheoradec. Due to the vagaries of -fPIC and dynamic linking, we wasting a _huge_ amount of time on function call overhead. We also take the opportunity to get rid of our wrapper around the old libogg API and implement the API we want directly. This gives more than an 18% decoding speed-up for an 82-byte net increase in code...

...ent one; Darwin Kernel 7.9.0). My understanding is that random number generators internally produce 32 bit integers, which then get converted into the desired distribution. I'm a little surprised there doesn't seem to be a way to get at them. Or is one supposed to do runif()*2^32-2^31? 3) Vagaries of the underlying C++ random number generator could also complicate life.

...mas should be handled in a general way to allow the same source code to work in different environments. I would like to propose that we focus on autolinking exclusively and that we divorce the implementation from the idea of "linker options" which, by nature, would tie source code to the vagaries of particular linkers. I don't see much value in supporting other linker operations so I suggest that the binary representation be a mergable string section (SHF_MERGE, SHF_STRINGS), called .autolink, with custom type SHT_LLVM_AUTOLINK (0x6fff4c04), and SHF_EXCLUDE set (to avoid the contents...

I've changed the subject line. It has nothing to do with my question with my original post, that no one seems to have any answer to, what file "image# 1" is looking for. This bloody email has now been blocked *twice*. Ljubomir Ljubojevic wrote: > On 01/09/2012 10:43 PM, m.roth at 5-cent.us wrote: >> Ljubomir Ljubojevic wrote: >>> On 01/09/2012 10:13 PM, m.roth at

...FileManager > is the right API layer to abstract at (it is too specific to Clang's > usage, and too hard to propagate through the rest of LLVM). My > intuition is that it is better to set out to define a lower level VFS > layer that is rich enough to support everything we do and the vagaries > of Win32/Unix, but is otherwise minimal. What about FileManager is too high level / too clang specific? The uniquing logic? The possibility to add in stats caches? Do you think we'd want to have a CachingFileSystem on top of the VFS layer? That would sound more orthogonal, on the other...

Hi all, I'm working with summary.gam() and noticed that the options()$width argument is ignored by some components of that function, in particular the formula, which is printed at an arbitrary length regardless of the desired width. I've tracked the problem back to print.formula(), so at a lower level than summary.gam(). Is there a way around this that I'm missing? library(mgcv) #

I am immediately reminded of something I read which goes "A sufficiently trained statistician can read the vagaries of a Q-Q plot like a sharman can read a chicken's entrails, with a similar recourse to scientific principles. Interpreting Q-Q plots is more a visceral than an intellectual exercise. The uninitiated are often mystified by the process. Experience is the key here." http://www.maths.murdoc...

https://bugzilla.mindrot.org/show_bug.cgi?id=1641 Summary: Add SELinux roles Product: Portable OpenSSH Version: 5.2p1 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: unassigned-bugs at mindrot.org ReportedBy: jchadima at redhat.com

...> is the right API layer to abstract at (it is too specific to Clang's >> usage, and too hard to propagate through the rest of LLVM). My >> intuition is that it is better to set out to define a lower level VFS >> layer that is rich enough to support everything we do and the vagaries >> of Win32/Unix, but is otherwise minimal. > > What about FileManager is too high level / too clang specific? The > uniquing logic? The possibility to add in stats caches? > Do you think we'd want to have a CachingFileSystem on top of the VFS > layer? That would sound mo...

Dear Listers, I am drawing a plot of two density curves, for male and female incomes. I would like to shade/hatch/color (whatever) the areas under the curves which are distinctive for each gender. This is the code I have tried so far: m <- density(topmal.d$y, bw = "sj") f <- density(topfem.d$y, bw = "sj") par(mfrow = c(1,1)) plot(x = c(0,400), y = c(0,0.02), type =