search for: misfunctioned

Dear all I would like to ask you if an assignment can be done inside a lapply statement. For example I would like to covert a double nested for loop for (i in c(1:dimx)){ for (j in c(1:dimy)){ Powermap[i,j] <- Pr(c(i,j),c(PRX,PRY),f) } } to something like that: ij<-expand.grid(i=seq(1:dimx),j=(1:dimy)) unlist(lapply(1:nrow(ij),function(rowId) { return

Being new to some aspects of BASH, I tried to reduce the quantity of scripts by introducing a comparison test into an existing working script. The script refused to work until I placed [ ] around the actual test. The second test, in the same script, misfunctioned until I removed the [ ] around the second test. ---------------------------- NON WORKING first comparison 5 if $dir="law" 6 then 7 www="law" 8 dir=${file:0:5} 9 else 10 www="www/s" 11 fi Error message = /root/bin/.us: line 5: law=law: comma...

....u22.net> wrote: > Being new to some aspects of BASH, I tried to reduce the quantity of > scripts by introducing a comparison test into an existing working > script. > > The script refused to work until I placed [ ] around the actual test. > The second test, in the same script, misfunctioned until I removed the > [ ] around the second test. > I think you are missing some very basic concepts here. First, the shell likes to parse things separated by white space. Second, [ is a synonym for test which is a build-in version of /bin/test, so try 'man test' for the syntax of...

Hello, I have been using the bitmap program for several years, for teaching purpose (introductory to elementary principles of information coding). At present, the program does not behave any longer as it should do : - after having clicked one of the drawing buttons (Point, Curve, Line, etc.) no drawing occurs inside the canvas area of the main window. This misfunction is observed when

Dear all, actually I installed CentOS 5.4 x86_64 on 11 new Dell R710 servers. It is required to use 5.4 to be covered by the NetApp Interoperability Matrix for use of Snapdrive. All systems spit out the error message mpt2sas0: failure at drivers/scsi/mpt2sas/mpt2sas_scsih.c:4637/_scsih_add_device()! at boot time. In dmesg the complete SCSI initialization logging appears as follows: SCSI

I am a little bit confused about the kernel support for oplocks. man page of smb.conf: ---------------- For UNIXs that support kernel based oplocks (currently only IRIX but hopefully also Linux and FreeBSD soon) this parameter allows the use of them to be turned on or off. This parameter defaults to "On" on systems that have the support, and "off" on systems that don't.