search for: reading

Hi All I have a TE110P card connected to a PRI line. In my zaptel.conf I have: span=1,1,0,esf,b8zs bchan=1-23 dchan=24 loadzone = us defaultzone=us and my zapata.conf is: [channels] context=inbound-pri switchtype = national pridialplan=unknown ;pridialplan=international signalling = pri_cpe callerid=asreceived busydetect=no usecallerid=yes hidecallerid=no callwaiting=no callwaitingcallerid=no

...1, ReadTotalTimeoutMultiplier -1 0.521030 Trying megatec protocol... 0.625036 send: 'Q1' 0.627036 w32_serial_read : ulen 512, vmin_ -1, vtime_ 0, hEvent 00000054 0.642037 w32_serial_read : characters are available on input buffer 0.647037 w32_serial_read : Reading 1 characters 0.651038 w32_serial_read : total characters read = 1 0.654038 w32_serial_read : Reading 2 characters 0.658038 w32_serial_read : total characters read = 3 0.661038 w32_serial_read : Reading 1 characters 0.664038 w32_serial_read : total characters read...

Hi, I compiled the latest version of ices from cvs, but I have some problems with it. When I start it up, I only get the error "Failed to read config file "/usr/local/icecast/etc/ices.conf"" My /usr/local/icecast/etc/ices.conf looks like this: <?xml version="1.0"?> <ices:Configuration xmlns:ices="http://www.icecast.org/projects/ices">

Hello, I would like to read sets of files within a folder, perhaps using recursive methods. Right now, I rename the files before import. It would be even better to do this without renaming files, without providing explicit filenames, perhaps by importing files based on chronology, and translating each filename into a header? Please excuse my ignorance, and help cure my clunky programming

I have a collection of .csv files in a directory, and want to read them into R data.frames whose names are the same as the file names, without the .csv extension e.g., from > (files <- list.files(pattern="*.csv")) [1] "Allstar.csv" "AllstarFull.csv" [3] "Appearances.csv" "AwardsManagers.csv" [5]

Hi all, When I ran the experiments to compare an application''s execution time in both a domU (named cctest1) and a native Linux machine (named ccn10), I noticed the application executes faster in domU. The host of the domU (named ccn9) and ccn10 are two nodes of a cluster and they have same hardware configurations. domU (cctest1) is created by exporting loopback files from dom0 on

Hi guys I gave these patches a try (on top of 2.6.23-rc9 plus the previously submitted 2.6.24 patch set). The last two seem to cause Badness on my system, whereby if I start a guest (using the same bzImage as the host, as before) it seems to boot OK, and the host system still superficially looks stable (my X session is OK and I can interact with existing processes) but if I attempt to launch any

Hi guys I gave these patches a try (on top of 2.6.23-rc9 plus the previously submitted 2.6.24 patch set). The last two seem to cause Badness on my system, whereby if I start a guest (using the same bzImage as the host, as before) it seems to boot OK, and the host system still superficially looks stable (my X session is OK and I can interact with existing processes) but if I attempt to launch any

We have many servers and we are using rsync to backup them. We are using it since a month, in one of the servers since a week did start loading alot the cpu, around 50 when the normal cpu load is less than 1. The odd thing is this wasnt hapening before. Today i ran the rsync and i straced it, below i pasted part of the strace, was tracing that almost an hour before i killed the process

Hi all, I'm trying to read a data set into R, but the file is messy, so I have to do it partially. The whole data is in a .txt file, and the values are separated by a space. So far ok. The problem is that in this file, not all the lines have the same number of elements, and the reading stops. And I loose the reading of the previous lines. ex. of data set: 11 12 13 21 22 23 31 32 33 34 41 42 43 44 51 52 53 61 62 63 64 71 72 73 74 75 81 82 (...) If I use the following: > aux <- read.table(file="data.txt", sep=" ",...

...R1C4 I added some white spaces as well as into R2C5 and R2C6 which a read in correctly by the read.xlsx function. read.table and read.delim seem not to be able to handle such files. Is there any workaround for that? Cheers -- View this message in context: http://r.789695.n4.nabble.com/Problems-reading-tab-delim-files-using-read-table-and-read-delim-tp4369195p4369195.html Sent from the R help mailing list archive at Nabble.com.

...wAuth #Allow Auth (identd)'' + read first rest + ''['' xAllowSMTP = xINCLUDE '']'' + echo ''AllowSMTP #Allow SMTP (Email)'' + read first rest + ''['' xAllowPOP3 = xINCLUDE '']'' + echo ''AllowPOP3 #Allow reading mail via POP3'' + read first rest + ''['' xAllowICMPs = xINCLUDE '']'' + echo ''AllowICMPs #Allows critical ICMP types'' + read first rest + ''['' xAllowIMAP = xINCLUDE '']'' + echo ''AllowIMAP #Allow re...

...Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-pc-solaris2.10"... Core was generated by `./asterisk -gc'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libcurses.so.1...done. Loaded symbols for /usr/lib/libcurses.so.1 Reading symbols from /usr/lib/libpthread.so.1... warning: Lowest section in /usr/lib/libpthread.so.1 is .dynamic at 00000074 done. Loaded symbols for /usr/lib/libpthread.so.1 Reading symbols from /usr/lib/libdl....

Hi! I don't know much about network programming, or about terminal handling. I wondered about why the command "scp file user at host:path" didn't work. It gave me the following error messages: "stdin: is not a tty" "Write failed flushing stdout buffer." "write stdout: Broken pipe" I tried it with different versions of ssh, first the newest debian

It seems like it works (partially?) with NUT/driver you mentioned. I will test it more when I return home. root at Failure:/lib/nut# ./nutdrv_qx -a test -x subdriver=fuji -u root -x productid=0000 -x vendorid=0001 -DDDDDD Network UPS Tools - Generic Q* USB/Serial driver 0.13 (2.7.2.5) USB communication driver 0.32 0.000000 debug level is '6' 0.001247 upsdrv_initups...

Hi all, When I ran the experiments to compare an application''s execution time in both a domU (named cctest1) and a native Linux machine (named ccn10), I noticed the application executes faster in domU. The host of the domU (named ccn9) and ccn10 are two nodes of a cluster and they have same hardware configurations. domU (cctest1) is created by exporting loopback files from dom0 on

...uot; to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-pc-solaris2.10"... > Core was generated by `./asterisk -gc'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /usr/lib/libcurses.so.1...done. > Loaded symbols for /usr/lib/libcurses.so.1 > Reading symbols from /usr/lib/libpthread.so.1... > warning: Lowest section in /usr/lib/libpthread.so.1 is .dynamic at 00000074 > done. > Loaded symbols for /usr/lib/libpthread.so.1 > Readin...

Dear R-Users, I noticed that *read* is not a generic function. Although it could benefit from the functionality available for generic functions: read = function(file, ...) UseMethod("read") methods(read) ?# [1] read.csv???? read.csv2??? read.dcf???? read.delim read.delim2? read.DIF???? read.fortran ?# [8] read.ftable? read.fwf???? read.socket? read.table The users would still

..."/lib/tls/libthread_db.so.1". Core was generated by `asterisk -vvvg -c'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/i686/libpthread.so.0...done. Loaded symbols for /lib/i686/libpthread.so.0 Reading symbols from /usr/lib/libncurses.so.5...done. Loaded symbols for /usr/lib/libncurses.so.5 Reading symbols from /lib/i68...

Hi guys, I found the troblue and fix it! I attached the patch. The trouble was in the command reply buffer use. You compute the value that value = reply[6]*256+reply[5] <- it's wrong The right solution: value = reply[5] * 256 + reply[6]; And other bug, battery.runtime compute, you divide this value 60 <- it's wrong right value: divide 1.0 I continue the work on this