search for: curretly

Hi, I've been following the changes in LLD's software architecture. Recently a new file was added: Alias.h In this file, the curret Atom set is extended with an AliasAtom. While the change seems innocent enough, it has some nasty potential. Simple.h and Alias.h are placed in the ReaderWriter component. This is the 2nd component in the layering: Driver ReaderWriter Passes Core The problem

Hi, recently I had to instal a new raid storage system for our central fileserver. It is connected by iscsi (1Gbit) and the fielsystems mounted are 400GB and 1TB and ext3. curretly about 400 GB are used by 1.5 Mio files. I turned quota on and did a quota check. BUT on reboot the system crashes/hangs during 'turning off quotas' This message shows up about 30++ sec after the shutdown ... Any idea? Hint? Suggestion? The storage is an SUN 7110 with SAS drives. The Se...

The inverted dependency of Core to ReaderWriter via Simple.h was already present. My idea was to fix the problem before it gets bigger. My proposal would be to move Simple.h and Alias.h to Core. Similar to UndefinedAtom.h etc. It would be even nicer to make the naming consistent as well, since there already is UndefinedAtom.h SharedLibaryAtom.h etc Maybe: SimpleAtom.h AliasAtom.h Moving the file

HI All. I have a linux box connected to a switch network with 2 network interfaces, how would I able to ''trunk'' these 2 interfaces? options I can see are: - ethernet bonding - iproute2? - teql Which one are the best to use? I''m curretly having problem with ethernet bonding, my setup are as follow: ip add: 192.168.10.30/24 I do: # modprobe bonding # ip addr add 192.168.10.30/24 dev bond0 # ifenslave bond0 eth0 # ifenslave bond0 eth1 # ip link set bond0 up At this stage, I can''t ping any of the other workstations / serve...

On Mon, Jun 2, 2014 at 12:49 AM, Rui Ueyama <ruiu at google.com> wrote: > I agree to move these files to Core. Any objections? None here. - Michael Spencer > > On Mon, Jun 2, 2014 at 12:44 AM, Bas van den Berg > <b.van.den.berg.nl at gmail.com> wrote: >> >> The inverted dependency of Core to ReaderWriter via Simple.h was already >> present. >> My

...Alternativly web pages could be used as is done now with some of the examples. Snippits would contain mostly rules (but perhaps content for the other files as well) and notes. So If you have Samba running on the FW you would have a snippit for that (as is curretly found on a page). Some possible snippit topics smtp, pop3 servers local news servers (including externally accessable customer support news servers). time servers integration with nove...

...ause it's posslble that there is a reference to the no-longer-needed object on the PROTECT stack, even though no one should actually be looking at it any more. In the current version of pqR (see pqR-project.org), modifications are (often) done in place for statements such as w = w * Q, but not curretly when the LHS variable does not appear on the RHS. Regards, Radford Neal

Has anyone at all gotten the Samab 3.0 to integrate into the FreeBSD 5.1 Name Service switcher? Are there patches avaliable? Does anyone know where to get the FreeBSD nss api so I can try to fix the code my self? I keep getting the following errors in my logs NSSWITCH(nss_method_lookup): winbind, passwd, getpwnam_r, not found

...no one should actually be looking at >> it any more. > > Can you explain this case? I don't think I understand it. > >> In the current version of pqR (see pqR-project.org), modifications are >> (often) done in place for statements such as w = w * Q, but not >> curretly when the LHS variable does not appear on the RHS. > > Yes, I looked at it earlier, and was excited to see that Luke had > ported half of your approach to standard R: > https://github.com/wch/r-source/blob/trunk/src/main/arithmetic.h#L65 > > But only the RHS temporary variables opt...

...e PROTECT stack, even though no one should actually be looking at > it any more. Can you explain this case? I don't think I understand it. > In the current version of pqR (see pqR-project.org), modifications are > (often) done in place for statements such as w = w * Q, but not > curretly when the LHS variable does not appear on the RHS. Yes, I looked at it earlier, and was excited to see that Luke had ported half of your approach to standard R: https://github.com/wch/r-source/blob/trunk/src/main/arithmetic.h#L65 But only the RHS temporary variables optimizations made it over. You...

I've run a new scan of LLD's architecture and it appears to be getting cleaner! There are still some upward dependencies however: - core depends on Reader and Writer - passes depend on Reader and Writer - ReaderWriter/PECOFF/ReaderCOFF.cpp depends on Driver.h The updated architecture can be seen here: http://www.c2lang.org/docs/lld_architecture_20140710.png On Tue, Jun 3, 2014 at 3:07

...s. Currently we have requirement of 20 simulataneous calls so we purchased 4 connections from the ISP. Giving us a total of 2 Mbps of upload b/w but spread over 4 different connections from the ISP. Each connection we buy from the ISP gives us the right to use one port on this CISCO 2950 switch. So curretly we have purchased 4 connections from the ISP and hence we have the right to use 4 ports on this switch. My three questions are: 1. Is there any technical reason behind why the ISP will not sell more then 512 Kbps of b/w on a single port to us ? 2. Can I do something to over come the restriction pu...

Hi, I would like to use Sweave to document a long function. Is it possible to split the function's code into chunks such that Sweave will accept each chunk without complaining. I have tried various approaches without sucess but I feel sure that someone has done this already. Here is one attempt ============== % First, define the funciton header <<defFunHdr, eval=FALSE>>= x <-

i did the debugging as you said. Kindly refer the following logs: (gdb) c Continuing. thread apply all bt [New Thread 0x7fc337c6b700 (LWP 29520)] Program received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () (gdb) thread apply all bt Thread 12 (Thread 0x7fc337c6b700 (LWP 29520)): #0 0x00007fc33509f18d in read () from /lib/x86_64-linux-gnu/libpthread.so.0 #1