search for: _sources_

Hola. Tengo un script con la siguiente estructura. #!/usr/bin/env Rscript args = commandArgs(trailingOnly=TRUE) source("carga-datos.R") source("modelo.R") y quiero llamar a mi script desde consola con Rscript --vanilla miscript.R datos1.csv De forma que se guarde como argumento el nombre del fichero que quiero cargar y se pase a al script carga-datos.R. El problema es

R-sig-Debian help, Yesterday I sought help regarding R upgrading from R-2.8.1 to R-2.9.1. I must thank specially Dirk for his helpful advice. But now I am facing a dilemma. I want to install a package called FLR which works under R-2.8.1. So my question is whether I can keep the latest release (R-2.9.1) and also install R-2.8.1 (and if feasible how.) Alternatively I could uninstall R-2.9.1 and

...t this time, but I made the addition to prevent that from happening. As a licensed station, we are responsible for our content and _must_ prevent racist content from airing. If we cannot do this, we will be shut down. <time-window>17:00-05:00</time-window> This option will restrict _sources_ from connecting to this stream outside the time window. We are required by law and contract to broadcast no more than 12 hours per day. Actually, we may broadcast all day, but only 12 hours worth of RIAA/GEMA/GVL music. I chose to limit source connection rather than listener connections because...

Hi, My R package has files in the 'inst' directory that it needs to reference. How can the R scripts in my package find out the full path to the 'inst' directory after the package is installed, given that different users may have installed the package to different libraries? Thanks, Jon Malmaud

I can't make sense of the connection stats on the admin page. We have one source and one mountpoint. What is the difference between _client_connections_ and _clients_ and _connection_s? How can they be so different in value? Same questions for _listener_connections_ and _listeners_? The connections values seem high for only 5 listeners and one admin. Here is a snapshot of the admin

Hi, Robert. I appreciate the explanation. Indeed, the terminology is not consistent or intuitive. So by your "4 services" you mean _sources_? If clients are source connections (one and the same?), then how do we reconcile limits for both clients and sources? Is it like saying, 'for all of the X sources, they can have a total of Y connections'? How can I set limits on the number of _listeners_? And this limit would be diffe...

> IMHO, a system like Icecast should be made so highly configurable that it > would fit everyone's needs, but I get the impression that only the needs of > the principal developers are of interest here. It makes me sad to see this, > Icecast could be great instead of just being good. > Melanie, As one of the 'principal developers', I don't think this is fair. Of

I have recently upgraded to Ubuntu Gutsy and, for the first time, am using a 64-bit installation. After failing miserably to install R from source, not a problem for me in the past with a 32-bit install, I went the route of using the Debian Etch build. This went smoothly, but I am unable to update my numerous R and BioConductor packages, getting non-zero exit status errors on each package. Is