Displaying 12 results from an estimated 12 matches for "myparamet".
Did you mean:
myparameter
2007 Mar 02
2
bending openssh output
.... Therefore
I modified the openssh source so it can be called from my source like a
function (simply changed "void main()" to "void ssh()"). This works
perfect for the moment, but now comes the problem:
When I use openssh to build up a connection to a ssh server like this:
ssh -myparameter pass user at host "ls -al * | grep .txt"
I usually get a single line returned like
-rw-r--r-- 1 user group 1223 2007-01-01 08:00 mydata.txt
Now my question:
Where in the openssh source can I redirect the output of this line from
stdout to a string variable I use? (so I could modify/...
2008 Apr 17
1
How to extract vectors from an arima() object and into a data frame?
This should be very easy, but alas, I'm very new to R. My end goal is to
calculate p-values from arima().
Let's say I just ran this:
> MyModel <- arima(y[1:58], order=c(1,0,0), xreg=MyData[1:58,7:14],
> method="ML")
> MyModel
And I see:
arima(x = y[1:58], order = c(1, 0, 0), xreg = MyData[1:58, 7:14], method =
"ML")
Coefficients:
ar1
2006 Jul 18
5
a best way to write this.
I have a form, with 3 fields, then in my controller I get the paramters
to run a query but I don''t want to filter with paramters if they are
nil or blank...
I''m doing this
@condition = ''''
if(params.....)
@condition = @condition + " myparamter = " + params[.....
if(params.....)
@condition = @condition + " myparamter = " +
2007 Jun 20
2
Retrieve part of (top right corner) of a "plot.data.frame" plot?
Hi,
I believe this question has been asked before, but I cant find and don't
remember the answer.
The problem is simple, calling 'plot.data.frame(x)' gives a nice 'matrix of
scatterplots' for each pair of columns in x. for example;
x <-
data.frame(a=jitter(01:20),
b=jitter(20:01),
c=jitter(21:40),
d=jitter(rep(01,20)),
2018 Jan 16
2
[nbdkit] Proposed (new) filter API
...fer-Encoding: 8bit
=encoding utf8
=head1 NAME
nbdkit-filter - How to write nbdkit filters
=head1 SYNOPSIS
#include <nbdkit-filter.h>
static int
myfilter_config (nbdkit_next_config *next, void *nxdata,
const char *key, const char *value)
{
if (strcmp (key, "myparameter") == 0) {
// ...
return 0;
}
else {
// pass through to next filter or plugin
return next (nxdata, key, value);
}
}
static struct nbdkit_filter filter = {
.name = "filter",
.config = myfilter_config,
/* etc */
};...
2018 Jan 19
0
[PATCH nbdkit filters-v2 2/5] Introduce filters.
...1 @@
+=encoding utf8
+
+=head1 NAME
+
+nbdkit-filter - How to write nbdkit filters
+
+=head1 SYNOPSIS
+
+ #include <nbdkit-filter.h>
+
+ static int
+ myfilter_config (nbdkit_next_config *next, void *nxdata,
+ const char *key, const char *value)
+ {
+ if (strcmp (key, "myparameter") == 0) {
+ // ...
+ return 0;
+ }
+ else {
+ // pass through to next filter or plugin
+ return next (nxdata, key, value);
+ }
+ }
+
+ static struct nbdkit_filter filter = {
+ .name = "filter",
+ .config = myfilter_config,
+ /* e...
2018 Jan 19
0
[PATCH nbdkit filters-v3 3/7] Introduce filters.
...0 @@
+=encoding utf8
+
+=head1 NAME
+
+nbdkit-filter - How to write nbdkit filters
+
+=head1 SYNOPSIS
+
+ #include <nbdkit-filter.h>
+
+ static int
+ myfilter_config (nbdkit_next_config *next, void *nxdata,
+ const char *key, const char *value)
+ {
+ if (strcmp (key, "myparameter") == 0) {
+ // ...
+ return 0;
+ }
+ else {
+ // pass through to next filter or plugin
+ return next (nxdata, key, value);
+ }
+ }
+
+ static struct nbdkit_filter filter = {
+ .name = "filter",
+ .config = myfilter_config,
+ /* e...
2018 Jan 14
10
[PATCH nbdkit INCOMPLETE 0/6] Introduce filters to nbdkit.
This patch isn't complete (patch 6/6 isn't finished) so it's just for
discussion, although it does compile and run.
This introduces to nbdkit a concept of "filters" which can be placed
in front of plugins to modify their behaviour. Some examples where
you might use filters:
* Serve a subset of the data, such as (offset, range) or a
single partition from a disk image.
2018 Jan 19
9
[PATCH nbdkit filters-v3 0/7] Introduce filters.
This is still tentative and needs a lot of work, but:
- partition filter works, supporting MBR & GPT
- prepare and finalize methods fixed
- open method can now be changed (allowing readonly flag to be modified)
- thread_model can be limited
I believe I made most of the changes which were previously suggested
in email. I think the only one I didn't was preventing inclusion of
both
2018 Jan 19
10
[PATCH nbdkit filters-v2 0/5] Introduce filters.
Rebased filters patch. Requires current git master + the locks /
thread model fix
(https://www.redhat.com/archives/libguestfs/2018-January/msg00128.html)
So a few changes here since last time:
The "introduce filters" and "implement filters" patches are
squashed together.
I introduced a concept of .prepare and .finalize. These run before
and after the data serving phase
2018 Jan 17
14
[PATCH 0/9] Add filters to nbdkit.
The first three patches are identical to:
https://www.redhat.com/archives/libguestfs/2018-January/msg00079.html
"[PATCH nbdkit v2 0/3] Refactor plugin_* functions into a backend"
The rest of the patches add filters using the new filter API
previously described here:
https://www.redhat.com/archives/libguestfs/2018-January/msg00073.html
This needs a lot more testing -- and tests --
2018 Jan 19
16
[nbdkit PATCH v2 00/13] Add filters + FUA support to nbdkit
A combination of the work that both Rich and I have been doing
lately, where filters use only the new API with flags on every
command that the client can send over the wire (we can then
add support for more flags in nbdkit without having to add new
callbacks, as NBD adds more flags upstream).
Eric Blake (4):
protocol: Split flags from cmd field in requests
backend: Pass flags argument through