search for: enpoints

...1+as.factor(endpoint)|trial/subject)) I beleive the fixed effects part of the code is okay. My intention for the random effects part is to estimate an intercept and treatment effect for each endpoint at the trial level. The correlation structure should produce a within correlation matrix for the enpoints at the subject level. Thus the random effects matrix is 4 by 4 and the within correlation matrix is 2 by 2 When i run the code in R, i get the following error message "Error in Initialize.corSymm(X[[2]], ...) : Initial value for corSymm parameters of wrong dimension&quot...

Is there the ability in the Asterisk 1.8 CEL logging to log the SIP endpoint IP as weell as the medie enpoint's ID's? Thanks Bryant -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100917/905bafb0/attachment.htm

Mongrelians, I''ve just posted a GemPlugin for Mongrel, which allows you to skip all header and status-code generation, effectively hijacking the socket for whatever your needs are, from inside the depths of any Rails, Camping, Merb etc application. http://mongrel-raw-out.rubyforge.org/ or gem install mongrel_raw_output I use the plugin at work, where the client insists that testing

On Samba AD DC most of these enpoint server are already running -- dcerpc endpoint servers = epmapper, wkssvc, rpcecho, samr, netlogon, lsarpc, spoolss, drsuapi, dssetup, unixinfo, browser, eventlog6, backupkey, dnsserver, mapiproxy Use samba-tool testparm -v first before adding them to the smb.conf I say this because I could not "join" Windows clients to Samba with these running

On 05/01/2015 12:03 PM, Rowland Penny wrote: > On 01/05/15 15:29, Steve Ankeny wrote: >> On Samba AD DC most of these enpoint server are already running -- >> >> dcerpc endpoint servers = epmapper, wkssvc, rpcecho, samr, netlogon, >> lsarpc, spoolss, drsuapi, dssetup, unixinfo, browser, eventlog6, >> backupkey, dnsserver, mapiproxy >> >> Use

On 01/05/15 15:29, Steve Ankeny wrote: > On Samba AD DC most of these enpoint server are already running -- > > dcerpc endpoint servers = epmapper, wkssvc, rpcecho, samr, netlogon, > lsarpc, spoolss, drsuapi, dssetup, unixinfo, browser, eventlog6, > backupkey, dnsserver, mapiproxy > > Use samba-tool testparm -v first before adding them to the smb.conf > > I say this

I have a NetGear FV318 living in my DMZ, with one of its LAN-ports living in my LOC zone. What rules are needed in shorewall to allow a certain subnet to make connections to this device from the net zone? Do I define it as a tunnel in shorewall/tunnels, or do I just allow some selected traffic to the DMZ IP? I am not sure which of the docs are right for me in this case?

Hello Mario , what if you try these : dcerpc endpoint servers = epmapper, wkssvc, rpcecho, samr, netlogon, lsarpc, spoolss, drsuapi, dssetup, unixinfo, browser, eventlog6, backupkey, dnsserver, remote, winreg, srvsvc auth methods = sam, winbind, ntdomain, ntdomain:winbind !! these are only for helping in debugging and should not be used in production. !! see all the e-mails with subject : Re: