search for: respecifi

Hello Puppet users, I had talked with Luke about this scenario and was wondering how others would/are handling something like this. Imagine a scenario where all servers will have a specific postfix configuration except for a server or two or three. So, you want to define a file "/etc/postfix/main.cf" and specify the source from your dist tree. But for those exceptional servers,

Dear all, I am trying to use the logistic regression with MCMClogit (package: MCMCpack/Coda) and I want to put a beta prior on the parameters, but it's giving me error message (please see output below) no matter what shape 1 or 2 I use. It works perfect with the cauchy or normal priors. Do you know if there is a catch there somewhere? Thanks logpriorfun <- function(beta,shape1,shape2){

hi there, right now i am going about things a round about route with graphs in that if i want to change the scale to log, I have to to a "reset" with add=F, then program things to be redrawn from scratch - bad coding basically:P in plot(), the first arguement it needs is data - how do you reference whats already there, rather than respecifying (or am i supposed to use a different

Hello, I've got what I'd expect to be a pretty simple issue: I fit an aov object using multiple error strata, and would like some significance tests for the contrasts I specified. In this contrived example, I model some test score as the interaction of a subject's gender and two emotion variables (angry, happy, neutral), measured at entry to the experiment (entry) and later

The ftable structure is not an ordinary matrix. Instead, it has the body of the table with several cbind- and rbind-ed rows and columns of label information. The example in ?ftable has two row factors and two column factors. Continuing with the example in ?ftable, enter tmp <- ftable(mtcars$cyl, mtcars$vs, mtcars$am, mtcars$gear, row.vars = c(2, 4), dnn =

Hi I am trying to do a large glm and running into this message. Error: cannot allocate vector of size 3725426 Kb In addition: Warning message: Reached total allocation of 494Mb: see help(memory.size) Am I simply out of memory (I only have .5 gig)? Is there something I can do? Stephen [[alternative HTML version deleted]]

I'm trying to create a graph using plot() with an axis that I essentially want to plot the categories in the reverse alphanumeric order - opposite of the typical R fashion. Is there a function to do this? In other words, I have categories "a", "c", "g", "z" which is the order they'll be plotted, but I want to plot them as "z",

Ariel, This area is a bit of a mystery to me too. I think the story is as follows and if it isn't please will someone who sees this correct me! Win95/98 and WinNT do not login to the server is the same way. Win95/98 works fine with a network login with Samba 1.9.18P10 and many previous versions, but WinNT requires a true NT Domain Controller to login. So with WinNT you cannot use server

I just made one of my 4.x remote servers inaccessible and just tested it on my 5.x laptop, and it does the same thing ... not sure if this is considered a 'desirable' effect, or a but ... but ... 'ifconfig <device> -alias' will wipe out all IPs on the device: mobile# ifconfig -a lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet 127.0.0.1 netmask

...have a question regarding conditions: I build a query using values from the params that were entered onto a web form using something like :conditions => [" foo like x and bar like y", params[:x]+"%", params[:y]+"%"] It would appear that the conditions need to be respecified on each page so I have had to remember them in the session: unless params[:page] session[:search] = ["category_id = ? and foo like ? and bar like ?", params[:item][:category_id], params[:item][:foo]+"%", params[:item][...

Hi everyone, say I have a function called 'foo', which takes the argument arg1. Is there any mechanism that I can use to "learn" about the variable where foo(arg1) is going to be stored? For example: x <- foo(arg1) so, inside foo() I'd like to be able to get the string "x". if, foo(arg1) was used insted, I'd like to get NA. thank you very much, b

Dear all, I've got a problem in including square variables in lme and lmlist functions. I've tried to work on Oxboys data of Pinheiro and Bates'book, which consist of the heights of 26 boys, each mesured on nine different occasions : > Oxboys Grouped Data: height ~ age | Subject Subject age height Occasion 1 1 -1.0000 140.50 1 2 1 -0.7479 143.40

dear all, I want to perform a posthoc test for my ANCOVA: a1<-aov(seeds~treatment*length) With summary(glht(a1, linfct = mcp(treatment = "Tukey"))) R tells me: "covariate interactions found -- please choose appropriate contrast" How do I build these contrasts? Ideally, I would like to have the posthoc test for the ANCOVA including a block-effect

Hi, I had a look at the MASS4 scripts in the MASS package, in Ch 11.3 Factor Analysis, there is a section of codes like: data(ability.cov) ability.FA <- factanal(covmat = ability.cov, factors = 1) ability.FA (ability.FA <- update(ability.FA, factors = 2)) #summary(ability.FA) round(loadings(ability.FA) %*% t(loadings(ability.FA)) + diag(ability.FA$uniq), 3)

In our environment home directories are auto-mounted via /home/<user> including on the server provided mail. Within the various mail services though we try to isolate and override with local /mail/home/<user> Works well except that dovecot still wants to cd to the real home triggering a useless and potentially hindering automount when it invokes the imap or pop3 process specified by

The Wine development release 1.1.27 is now available. What's new in this release (see below for details): - New version of the Gecko engine. - New GSM 06.10 codec support. - Improved support for the disk volume APIs. - Support for XShm pixmaps for better performance. - Various bug fixes. The source is available from the following locations:

This is v3 of my disk series. What were previously patches 01-06 have been applied. These are the tested and updated remainder, addressing the previous comments. 1 Preparatory work. 2-4 The new parser and its documentation. 5-6 Replace old parsers with calls to the new one. 7-8 Two features, one of them essential. 9 Basic test suite for disk string parsing, as adhoc script.