search for: _not_

Can anyone comment on the following results from running a test program we've writen for PostgreSQL? Should the following be thread-safe, either as themselves, or a different function we should be calling? Your gethostbyname() is _not_ thread-safe Your getpwuid() is _not_ thread-safe

...;" feature, the only problem is that i can't use an ip-number in authorized_keys (because i do not know it). In an interactive shell, the env variable 'SSH_CLIENT' is set, and this variable can easily be parsed for the connecting ipnumber. The real problem is that this variable is _not_ set when just executing a remote command. Is it possible to retrieve the ipnumber of the connecting client while executing a remote command? Simply turning on the enviroment variables should suffice. im using OpenSSH version 2.2.0p1 on Debian GNU. gr, Sendy De Graaf sendy at dds.nl

...lease use an appropriate SYNC_* barriers instead of > heavy bold hammer. That stuff was design explicitly to support the > requirements of Documentation/memory-barriers.txt That's madness. That document changes from version to version as to what we _think_ the actual hardware does. It is _NOT_ a specification. You cannot design hardware from that. Its incomplete and fails to specify a bunch of things. It not a mathematically sound definition of a memory model. Please stop referring to that document for what a particular barrier _should_ do. Explain what MIPS does, so we can attempt to...

...lease use an appropriate SYNC_* barriers instead of > heavy bold hammer. That stuff was design explicitly to support the > requirements of Documentation/memory-barriers.txt That's madness. That document changes from version to version as to what we _think_ the actual hardware does. It is _NOT_ a specification. You cannot design hardware from that. Its incomplete and fails to specify a bunch of things. It not a mathematically sound definition of a memory model. Please stop referring to that document for what a particular barrier _should_ do. Explain what MIPS does, so we can attempt to...

...is exactly zero. The factorization *> has been completed, but the factor U is exactly *> singular, and division by zero will occur if it is used *> to solve a system of equations. Accordingly, when INF0>0, determinant(A) behaves as det(A)=0, _not_ computing prod(diag(U)). The problem here is that DGETRF can _also_ give positive INFO for matrices containing NaN, which may very well not be singular for some finite value of NaN. I claim that, when INFO>0, determinant(A) should _not_ behave as det(A)=0 unconditionally, but rather sometimes...

Nick, What are you planning on running over the shared connection? Database, eMail, File Shares? How many users? How much data? What is your I/O profile? I've worked with 'enterprise' storage most of my career either as a consumer, adviser or provider - can't comment on AoE other than to suggest you look at what are the business & technical goals, how they solve it and what

Hi everybody, Is the only way to use asterisk _not_ as root to change the permission of all the directories where asterisk need to create a file? ("/var/run/", "/var/log/asterisk/messages") any help will be appreciated, Cyprien

Hi, is there any way to install extlinux on a _not_ mounted ext4 image? I can easily write the extlinux.sys manually to a fixed inode, and prepend a prebuild mbr, but is there anything else i am missing? patch_file_and_bootblock does a couple of magic things, that are beyond me. The devices are simple images that run in virtualbox, so do i real...

...what you saw? Yep, exactly. > I wonder if the fix should be changing the inner if to: > if (IP[-1].valno != LHSValNo) { > ReplacedValNos.push_back(IP[-1].valno); > IP[-1].valno = LHSValNo; > } I was thinking along the same lines. But does this work for the cases where IP is _not_ end()? Is it true that we always want to look one back from IP? -Dave

On Wednesday 30 January 2008 16:22, Evan Cheng wrote: > > I was thinking along the same lines. But does this work for the > > cases where > > IP is _not_ end()? Is it true that we always want to look one back > > from IP? > > I think so. That's the intention and it's safe because IP != begin(). Right. But doesn't that imply we've had some messed up intervals being created for quite some time, even onces where IP was _...

The following are new Lua c32 modules in 6.03-pre*: cmenu.c32: cpu.c32: dhcp.c32: dmi.c32: lfs.c32: pci.c32: syslinux.c32: vesa.c32: I am wondering whether the following modules, which are _not_ new and are also included in 6.03-pre*, have _any_ relation either to the above list or to Lua: cpuid.c32: cpuidtest.c32: dmitest.c32: pcitest.c32: vesainfo.c32: TIA, Ady.

From: Rodrigo Barbosa <rodrigob at suespammers.org> > Btw, don't quote me on this one :) > I'm only 90% sure of the hotswapping capabilities, and less than 50% > sure about the price :) There _are_ systems with hot-swap CPUs, memory and/or, PCI[-X] slots. They are _not_ commodity and pricey, and require OS-level support. In fact, I believe Linux 2.6 has some support for hot-swap -- at least at the PCI[-X] level, if not memory and possibly CPU as well. It requires extensive support though for that type of "dynamic" flexibility. -- Bryan J. Smith ma...

...Red Hat doing this, then you'll want to complain about a number of distributors well before Red Hat who are far worse. > The GPL covers anything that can be considered a derivative work under > copyright law. That certainly includes binaries. Now you're mixing things. The GPL does _not_ address binaries, just what is required -- availability of source, and no restrictions on that source for things that are required for that source to work -- _regardless_ of what is redistributed. It also states that you can't use GPL source with someone non-GPL that requires it to function....

...d remove identity moves instructions: bool LiveIntervals::runOnMachineFunction(MachineFunction &fn) { ... // perform a final pass over the instructions and compute spill // weights, coalesce virtual registers and remove identity moves but the data structure LiveVariables::VirtRegInfo is _not_ updated. That is, VarInfo::DefInstr may point to an invalid (being coalesced) instruction. -- Tzu-Chien Chiu, 3D Graphics Hardware Architect <URL:http://www.csie.nctu.edu.tw/~jwchiu>

...part, because to me is seems to conflate what the >indices vs. name operands in DAGs are for. We can often think of DAG >operators as functions, and the operands are arguments of the >function. So using a numeric index would return an argument of a given >index. However, the $names are _not_ names of function arguments! They >are a mechanism for tagging DAG nodes that are interesting as part of >pattern matching. > >So please don't add this functionality, and definitely don't add it in >this way. If there is a convincing reason for extracting DAG nodes by >nam...

..... > You really need an independent architect to come in and make your > life easier. Because it seems your department isn't aware of all your > interoperability options. I want to point out one thing. Understand Samba is a collection of services designed of and for CIFS/SMB. It is _not_ a complete "enterprise directory solution." Samba includes: - A Legacy Registry-SAM compatible password store - A Legacy NetBIOS-WINS naming service and protocol - A Legacy NTLM (NT LAN Manager) authentication protocol And then "wraps into" traditional UNIX services like UNI...

...comment # some good lines a <- 1 # a bad line stop('an error') # another good line b <- 2 ", file=codefile) # with source() the line number is displayed source(codefile) traceback() tryCatch(source(codefile), error= function(e){ str(e) }) # with sys.source() the line number is _not_ displayed e <- new.env() sys.source(codefile, e) traceback() sessionInfo() ##### # output ##### > codefile <- tempfile() > write("# some comment + # some good lines + a <- 1 + # a bad line + stop('an error') + # another good line + b <- 2 + ", file=codefile) &...

...Documentation/memory-barriers.txt and had no chance to know what you > > use it in this way too. > > Well, Documentation/memory-barriers.txt was intended as a guide for Linux > kernel hackers, and not for hardware architects. Yeah, this goes under the header: memory-barriers.txt is _NOT_ a specification (I seem to keep repeating this). > ------------------------------------------------------------------------ > > commit 955720966e216b00613fcf60188d507c103f0e80 > Author: Paul E. McKenney <paulmck at linux.vnet.ibm.com> > Date: Thu Jan 14 14:17:04 2016 -0800...

...Documentation/memory-barriers.txt and had no chance to know what you > > use it in this way too. > > Well, Documentation/memory-barriers.txt was intended as a guide for Linux > kernel hackers, and not for hardware architects. Yeah, this goes under the header: memory-barriers.txt is _NOT_ a specification (I seem to keep repeating this). > ------------------------------------------------------------------------ > > commit 955720966e216b00613fcf60188d507c103f0e80 > Author: Paul E. McKenney <paulmck at linux.vnet.ibm.com> > Date: Thu Jan 14 14:17:04 2016 -0800...

I have a 10 blade cluster of just hardware - I can install what I want, how I want. ? What options are there if I wanted to build the 10 blades as one large beast, but _NOT_ necessarily for someone doing grid-type work? ? ?Some users don't now how to program that way, but they'd like to have their program run on something that acts like a single processor, but a massive single processor with lots of memory. ?Some code is designed for a single, powerful workstat...