Displaying 20 results from an estimated 766 matches for "consequential".
2011 Jul 19
4
Samba Share Access denied on Solaris
...the addressee. If you have received this message in error, please notify the system manager/sender. Any unauthorized use, alteration or dissemination is prohibited. The Department of Water Affairs and Forestry further accepts no liability whatsoever for any loss, whether it be direct, indirect or consequential, arising from this e-mail, nor for any consequence of its use or storage.
2003 Jun 26
3
Request for option for use on an unreliable connection
I have been using rsync for the last year or so. Generally I am very
pleased with the performance and features, but I am forced to use a
rather unreliable link to one of my mirrors. Consequentially rsync often
bails out with a protocol error in the middle of a large session due to
transient misbehaviour on the link. This appears to abort the whole
transfer. One solution would appear to be an option to log the error
then attempt the next file in the set. Is there a patch to allow this?...
2020 Aug 20
0
[PATCH nbdkit 01/13] common/replacements: Replace missing functions using LIBOBJS.
...;' AND
+# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
+# THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+# PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL RED HAT OR
+# CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
+# USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY...
2020 Aug 18
0
[PATCH nbdkit 3/9] server: Add general replacements for missing functions using LIBOBJS.
...;' AND
+# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
+# THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+# PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL RED HAT OR
+# CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
+# USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY...
2004 May 06
3
[LLVMdev] Plea for help
...t;math.h>
int main() {
std::cerr << std::numeric_limits<float>::infinity() << "\n";
std::cerr << HUGE_VAL << "\n";
}
[finna at coplin11 ~/test]$ g++ tst.cpp
[finna at coplin11 ~/test]$ ./a.out
0
inf
[finna at coplin11 ~/test]$
But making the consequential changes in LLVM seems trickier.
Do you plan to correct it in CVS, or is there a path I can follow
to fix it myself on my own installation ?
Best regard
/Finn
2013 Feb 17
4
why are qemu-img and vhd-util created files incompatible?
I was wondering if someone can shed some light on why vhd files
created with qemu-img don''t really work right with vhd-util and
consequentially blktap in general. To validate the incompatiblity its
simple enough to do
qemu-img create -f vpc test.vhd 40g
vhd-util snapshot -n child.vhd -p test.vhd
Which will show the below and then the headers don''t display the BATMAP summary:
primary footer invalid: creation time in future
te...
2018 Aug 01
2
Re: [PATCH v2 nbdkit 4/6] common: Add a directory for common code shared by plugins and filters.
...PRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
> +# THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
> +# PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL RED HAT OR
> +# CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
> +# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
> +# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
> +# USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
> +# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
> +# OR TORT (INCLUDING NEGLIGENCE OR OTHERW...
2020 Apr 10
0
[PATCH nbdkit UNFINISHED] Add the ability to write plugins in golang.
...;' AND
+# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
+# THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+# PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL RED HAT OR
+# CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
+# USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY...
2015 Jul 02
6
boot... round 2
Hi,
hpa wrote:
> On PowerPC (I think) "unsigned char" is the default.
In any case it seems a good idea to interpret the character
more explicitely. To my experience, one signdness change causes
a little tree of consequential signedness changes or questionable
cast operations.
How about the following instead ?
if ((c >= 0 && c <= ' ') || c == '\x7f') {
Besides code improvement there is the riddle of how gcc 5
can spoil the result.
> gcc does have an -funsigned-char option.
So ques...
2006 Dec 23
4
AltGr not working in R GUI Script Editor (PR#9430)
...duced by pressing key
combinations AltGr+F, AltGr+G, AltGr+B and AltGr+N, respectively. These
combinations generally work in all Windows programs and also in R Console.
However, R Script editor produces behaves wrongly and causes:
AltGr+F to open Find dialog box,
AltGr+N to open new Script window.
Consequentially, it is not possible to type ] and } brackets using slovenian
input settings in script editor. Meanwhile, AltGr+G and AltGr+B work fine.
2020 Apr 21
2
[PATCH nbdkit v2] Add the ability to write plugins in golang.
...;' AND
+# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
+# THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+# PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL RED HAT OR
+# CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
+# USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY...
2004 Jun 18
5
Lag on network using Samba
...tion and use only of the addressee.
Should you have received this e-mail in error, please delete
and destroy it and any attachments thereto immediately.
Under no circumstances will the Cape Technikon or the sender
of this e-mail be liable to any party for any direct, indirect,
special or other consequential damages for any use of this e-mail.
For the detailed e-mail disclaimer please refer to
http://www.ctech.ac.za/polic or call +27 (0)21 460 3911
2005 May 18
1
loop
Rather than using a loop, how can I remove all consequentially
repeated values as in this example?
I am guessing using diff would help but not quite sure how.
> get
> s
date f
1 1999-01-01 1
2 1999-01-02 1
3 1999-01-03 1
4 1999-01-04 2
5 1999-01-05 2
> v <- s[1,'f']; for (i in 2:nrow(s)) { if (s[i,'f'] == v) s...
2003 Jun 02
2
R 1.7.1 beta is out
I've wrapped up the first beta release of 1.7.1. It is available on
http://cran.us.r-project.org/src/base/
Things are set up so that a new version should be generated every
morning at 7am local time (Wisconsin), until the day of the final
release. (And consequentially, although it will propagate to the rest
of CRAN, it will most likely be out of date by then, so do get it from
the above address.)
--
O__ ---- Peter Dalgaard Blegdamsvej 3
c/ /'_ --- Dept. of Biostatistics 2200 Cph. N
(*) \(*) -- University of Copenhagen Denmar...
2004 May 06
0
[LLVMdev] Plea for help
...t; std::numeric_limits<float>::infinity() << "\n";
> std::cerr << HUGE_VAL << "\n";
> }
> [finna at coplin11 ~/test]$ g++ tst.cpp
> [finna at coplin11 ~/test]$ ./a.out
> 0
> inf
> [finna at coplin11 ~/test]$
>
> But making the consequential changes in LLVM seems trickier.
> Do you plan to correct it in CVS, or is there a path I can follow
> to fix it myself on my own installation ?
The easy way to do it in your area is to replace all occurences of
std::numeric_limits<float>::infinity() with HUGE_VAL. The only two files...
2018 Aug 01
0
[PATCH v2 nbdkit 4/6] common: Add a directory for common code shared by plugins and filters.
...;' AND
+# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
+# THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+# PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL RED HAT OR
+# CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
+# USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY...
2018 Aug 01
0
Re: [PATCH v2 nbdkit 4/6] common: Add a directory for common code shared by plugins and filters.
...RANTIES, INCLUDING, BUT NOT LIMITED TO,
> > +# THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
> > +# PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL RED HAT OR
> > +# CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
> > +# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
> > +# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
> > +# USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
> > +# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
> > +# OR TORT (INCLUDING...
2020 Mar 26
0
[PATCH nbdkit 5/9 patch split 1/5] Create libnbdkit.so.
...;' AND
+# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
+# THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+# PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL RED HAT OR
+# CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
+# USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY...
2020 Apr 10
3
[PATCH nbdkit UNFINISHED] Add the ability to write plugins in golang.
Sorry Dan, but I really do dislike golang with a passion :-)
Here is a patch that allows you to write nbdkit plugins in golang. As
with C, OCaml and Rust, you can write a plugin in Go which compiles
directly to a .so file that can be loaded into golang, so in that
sense it works completely differently from scripting language plugins
like Perl and Python where there's an
2019 Sep 28
0
[PATCH nbdkit v2 4/4] info: Add tests for time, uptime and conntime modes.
...;' AND
+# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
+# THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+# PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL RED HAT OR
+# CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
+# USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY...