Displaying 20 results from an estimated 8753 matches for "routined".
Did you mean:
routine
2004 Aug 23
1
Problem with mysql and with asterisk
Hi Every one and Lerale Erwan
I have briefly describe my problem and I have provide the steps as follows:
I have intalled redhat properly and from the konsole I checked with mysql.
"rpm -qa | grep mysql" and the konsole provide me the message:
mysql-3.23.54a-11
mysql-server-3.23.54a-11
Then I have download the asterisk and addons:
By the using of :
cd /usr/src
export
2013 Jan 17
1
Fwd: Re: Inconsisten declaration of ssh_aes_ctr_iv()
Oops, I meant to CC the list on this.
--
Iain
----- Forwarded message from Iain Morgan <Iain.Morgan at nasa.gov> -----
Date: Thu, 17 Jan 2013 14:51:01 -0800
From: Iain Morgan <Iain.Morgan at nasa.gov>
To: Damien Miller <djm at mindrot.org>
Subject: Re: Inconsisten declaration of ssh_aes_ctr_iv()
On Wed, Jan 16, 2013 at 21:26:39 -0600, Damien Miller wrote:
> On Mon, 14 Jan
2004 Apr 12
1
Voicemail config from database
Any help with this will be greatly appreciated. When re-compiling * to
include voicemail access from a MySQL database, I recieve the follwing
error. Anybody know how I can fix this? Am I missing packages somewhere?
app_voicemail.c:44:25: mysql/mysql.h: No such file or directory
In file included from app_voicemail.c:247:
mysql-vm-routines.h:7: parse error before '*' token
2013 Feb 22
1
Registering native routines
I'm working on registering all the routines in the survival package, per a request from
R-core. Two questions:
1. In the coxph routine I have this type of structure:
if (survival has 2 columns) routines <- c("coxfit5_a", "coxfit5_b", "coxfit5_c")
else routines <- c("agfit5_a", "agfit5_b",
2016 Apr 15
2
Randomly SSL Errors since upgrade to 2.2.23-1 (Enterprise Edition)
Hi,
first of all, many thanks for a great piece of software.
Today I updated one of our 2 IMAP/POP3 proxies from version 2.2.15.17-1 to 2.2.23.1-1 (both are enterprise editions).
After the update I now see randomly the following errors in the log file on my first proxy:
...
Apr 15 10:28:54 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:1408F119:SSL
2011 Apr 11
2
[LLVMdev] RFC: GSoC Project
Hi!
Thanks for the feedback. For context, my implementation plan is here:
http://pastebin.com/e9JMZNCE
First, about unwinding:
In architectures like x86-64, where unwinding based on DWARF info, there
shouldn't be any problems; since the DWARF info will be emitted
correctly. Otherwise, if the unwinding is done by following BP, it
should still be possible to have BP de-reference correctly
2011 Feb 07
2
fast optimization routines in R
Dear R help archive group,
I am looking for a maximization routine that I can use to maximize a large
variety of relatively complex likelihoods. I undertand (from previous posts)
that coding the objective function more efficiently can help. However, the
optimization routine employed seems important too. So far, I have tried the
optimization routines optim, maxlik, trust and nlminb. The latter two
2005 Aug 28
2
xerbla called from BLAS routine (PR#8100)
Full_Name: G?ran Brostr?m
Version: R-2.1.1, 2.2.0
OS: Debian unstable
Submission from: (NULL) (213.65.9.59)
Some BLAS routines call xerbla for error messages, which results in a message
like
"LAPACK routine DGER gave error code -9".
Suggested solution: In
void F77_NAME(xerbla)(char *srname, int *info)
{
/* srname is not null-terminated. It should be 6 characters. */
char
2011 Apr 11
0
[LLVMdev] RFC: GSoC Project
On Mon, Apr 11, 2011 at 9:07 AM, Sanjoy Das
<sanjoy at playingwithpointers.com>wrote:
> Hi!
>
> Thanks for the feedback. For context, my implementation plan is here:
> http://pastebin.com/e9JMZNCE
>
> First, about unwinding:
>
> In architectures like x86-64, where unwinding based on DWARF info, there
> shouldn't be any problems; since the DWARF info will be
2005 Oct 10
1
passing char to Fortran routine
Hello all,
I am using an existing Fortran routine that takes a single character string
as argument. The routine echoes the argument that I provide. When working on
OS X 3.9 there seems to be no problem, ie the Fortran routine nicely echoes
my argument. However, I compiled the same package on a PC (using all the
tools provided in the R for windows faq), and the routine only echoes the
first letter
2006 Jan 20
1
stack level too deep from has_many / belongs_to relationship
I have the following 3 models (2 models joined by an intermediate):
1. class Exercise < ActiveRecord::Base
2. has_many :routines, :class_name=>''RoutineExercise''
3. end
1. class Routine < ActiveRecord::Base
2. has_many :exercises,
3. :class_name=>''RoutineExercise'',
4. :order=>''position''
5. end
1. class
2017 Feb 14
6
Registration of native routines
Registration of 'native routines' (entry points in compiled code loaded
into R) has been available for over 14 years, but few packages make use
of it (less than 10% of those on CRAN with compiled code).
Registration has similar benefits to name spaces in R code:
- it ensures that the routines used by .C, .Call etc are those in your
package (without needing a PACKAGE argument).
- it
2011 Apr 11
2
[LLVMdev] RFC: GSoC Project
On Mon, Apr 11, 2011 at 7:34 AM, Justin Holewinski <
justin.holewinski at gmail.com> wrote:
> On Mon, Apr 11, 2011 at 9:07 AM, Sanjoy Das <
> sanjoy at playingwithpointers.com> wrote:
>
>> Hi!
>>
>> Thanks for the feedback. For context, my implementation plan is here:
>> http://pastebin.com/e9JMZNCE
>>
>> First, about unwinding:
>>
2006 Apr 21
4
programming advice?
Dear R-helpers:
I am doing some exploratory programming and am considering a routine that
has several other routines defined within it, so that I can avoid a large
and messy global re-programming to avoid naming conflicts.
My question is this: Because it is interpreted, does R have to re-build
these internal routines every time the new routine is called? I'm not
overly worried right now
2005 Dec 07
0
organizing plot drawing routines; creating complex expressions
Hi,
My general goal is to find a coding strategy to efficiently store and
retrieve drawing routines for different plots.
This is my approach so far. In a single text file I store multiple drawing
routines where each routine draws a different plot.
A drawing routine may look like this:
panel.mean <- function(means,...){
dots <- list(...)
2007 Oct 02
4
R routines vs. MATLAB/SPSS Routines
Hi all,
I've become quite enamored of R lately, and have decided to try to teach
some of its basics (reading in data, manipulation and classical stats
analyses) to my fellow grad students at the University of Toronto. I
sent out a mass email and have already received some positive
responses. One student, however, wanted to know what differentiates the
routines that R uses, from those
2004 Sep 14
3
memory allocation questions
Dear R-devel
This one seems a bit arcane for R-help. I very often use R to call routines written in Delphi (son of Pascal), doing "persistent" memory allocation within Delphi. That is, I start R and load the Delphi DLL; then I use .C to call a Delphi routine which allocates a piece of memory X and returns to R a pointer to X; then I do some more stuff in R; then I call another Delphi
2015 Aug 04
13
[PATCH] efi: leaving long mode in kernel_jump routine
Syslinux 6.03 (efi64) fails to boot a 32-bit kernel. The way Syslinux
leaves long mode in kernel_jump assembly routine does not follow AMD64
specifications. More precisely:
1. After setting a new GADT, `cs` has to be refresh by doing a long
jump, but it is not
2. Other segments have to be updated, but they are not
3. Disabling paging has to be done before disabling long mode, but the
2018 Nov 05
2
errors in mail.err related with ssl
Hi. I have in mail.err file lines like below:
Nov 5 08:40:00 s1 dovecot: imap-login: Error: SSL: Stacked error:
error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request
Nov 5 08:40:00 s1 dovecot: imap-login: Error: SSL: Stacked error:
error:1408A10B:SSL routines:ssl3_get_client_hello:wrong version number
Nov 5 08:40:05 s1 dovecot: pop3-login: Error: SSL: Stacked error:
2009 Feb 15
2
Passing environments: why doesn't this work???
This is a trivial example I set up to see if I could pass an environment and
use the variables in it
(this is for a function that will be called many times and might need to use
a lot of variables that
won't be changing, so it seemed more sensible to use an environment).
Here's the code:
#########################
#The outer function
run.internal.env <- function(x) {
in.env <-