search for: noisily

On Wed, 28 Sep 2016 10:09:28 -0300 Gilberto Nunes via samba <samba at lists.samba.org> wrote: > Thanks.... I hope this is my last post with this matter! I hope it's your last post on any matter. You quit Samba very noisily. If you don't remember doing so, just look at the subject line. Don't look back. Go to your beloved Windows CIFS. You've found somebody better: Move on and don't keep pestering your ex. To everyone else: Around the turn of the century Samba had a web-app (CGI probably) to configur...

...e those who still use something that outdated in their products are either dead, or simply don't care about their customer's security (which is typical in the embedded devices area). Just by us (or anyone else) saying anything, that won't change. > The best we can do is deprecate as noisily as > possible after extremely generous grace period. This is what we are > doing I think just deprecating is what has been done years ago - everyone can by now truly know that SSH1 should not have been used since a long time. I'd even support if you really remove the v1 related code from...

The manual says that without --recursive directories are (noisily) skiped. However with --relative intermediate directories are created. So what happens if you give only -R? Is -d the default? And what happens when you give -R --no-dirs? I tried and it seems that intermediate dirs are considered anyway, so it looks like -R overrides --no-dirs. Is it true? Does it...

...;> On Wed, 28 Sep 2016 10:09:28 -0300 >> Gilberto Nunes via samba <samba at lists.samba.org> wrote: >> >> >> >>> Thanks.... I hope this is my last post with this matter! >>> >> I hope it's your last post on any matter. You quit Samba very noisily. >> If you don't remember doing so, just look at the subject line. >> >> Don't look back. Go to your beloved Windows CIFS. You've found >> somebody better: Move on and don't keep pestering your ex. >> >> To everyone else: Around the turn of the ce...

...USY), this indicates + * that the lock is held somewhere. That means a programming + * error if the main program is using threads. + */ + errno = r; + perror ("guestfs_close: g->lock"); + /* While we're debugging locks in libguestfs I want this to fail + * noisily. + */ + abort (); + } + if (g->trace) { const char trace_msg[] = "close"; @@ -403,21 +435,6 @@ guestfs_close (guestfs_h *g) free (g->append); guestfs_int_free_error_data_list (g); gl_tls_key_destroy (g->error_data); - r = glthread_recursive_lock_destro...

On Jul 9, 2014, at 11:24 AM, Ted Mittelstaedt <tedm at mittelstaedt.us> wrote: > Someone could write a driver for MODBUS for NUT, all of the information > and materials are available to do it. The simple fact of it is that the > reason no one has done so is that the apcupsd program is available. You're right, it's the microlink protocol that they have been promising to

...k another two years would make an > > > appreciable change to the numbers you posted above, beyond old > > > hardware literally dying of old age? > > Our ability to influence people who run truly obsolete software is > extremely limited. The best we can do is deprecate as noisily as > possible after extremely generous grace period. This is what we are > doing > > -d >

...ion can fail in several ways but most notable if the server doesn't support querying extents. In this case VDDK raises an error message through the error_function callback, which we turn into a call to nbdkit_error. In most cases this will cause something to be printed to stderr and/or logged noisily to syslog, which is not desirable. This commit adds a per-thread error suppression mechanism so that we can temporarily hide errors, especially while doing this test, but I guess it might be useful in future in other cases too. Note this only affects a narrow range of versions of VMware ESXi and...

There's a world of difference between changing defaults and killing functionality. SSH in general and OpenSSH in particular is part of what we'll eventually get around to identifying as (I know everyone hates this word) critical infrastructure. That means it doesn't break, particularly not intentionally, and even more particularly not without time, warning, and probably public input.

...ing the standard PDC HID protocols, and even testing against > NUT, whereas APC has been much more of a moving target. I don't > believe I accused APC of malice in their innovation, but if it sounds > like I am frustrated with that situation, I am. > I understand the frustration! I noisily complained on the apcupsd forum for several years about the situation. Now I'm noisily complaining on the NUT forum about the situation. ;-) Fact is I use both apcupsd and NUT. Anyway, APC is under the impression that NUT is sponsored by MGE/Eaton. So, it interests me to read: "..Today...

Ok. I seem to be having some real problems today :) There is a link from the main page straight to the Wx::Frame tutorial, under the NEWS section. http://wxruby.rubyforge.org/wiki/wiki.pl Sorry for wasting everyone''s time :( Robert _________________________________________________________________ Getting married? Find tips, tools and the latest trends at MSN Life Events.

I’ve seen this done in the past without compiler support (for the case of handwritten or JIT’d, etc functions that need checking). It worked something like this: 1. Pass calls to the risky functions through a macro/template or such. 2. In release mode, this turns into a no-op. In debug mode, this sends the calls through a handwritten asm wrapper that sets all the callee-save registers to random

...big concerns I had back when the dual licensing happened in the first place. > Anyways, there seem to be a few, all somewhat bad options left to us with ASan/TSan and similar more "advanced" runtimes: > > 1) Swallow the lame binary attribution clause requirement. Document this noisily. > 2) Require they are build as DSOs, and thus the attribution restricted to that runtime library entity. Maybe 2a: engineer asan so that it *optionally* links to the DSO. If the DSO is present, functionality is enabled, if not, it is silently disabled and the app still works (at some performa...

...d back when the dual licensing happened in the first place. > > > Anyways, there seem to be a few, all somewhat bad options left to us with > ASan/TSan and similar more "advanced" runtimes: > > 1) Swallow the lame binary attribution clause requirement. Document this > noisily. > 2) Require they are build as DSOs, and thus the attribution restricted to > that runtime library entity. > > > Maybe 2a: engineer asan so that it *optionally* links to the DSO. If the > DSO is present, functionality is enabled, if not, it is silently disabled > and the app...

...ssues, I suspect making this bucketing more clear would simplify some of these projects.... Anyways, there seem to be a few, all somewhat bad options left to us with ASan/TSan and similar more "advanced" runtimes: 1) Swallow the lame binary attribution clause requirement. Document this noisily. 2) Require they are build as DSOs, and thus the attribution restricted to that runtime library entity. 3) Build the functionality needed by ASan/TSan/etc independently of LLVM's core libraries. Code duplication here, and only a dim hope that we could package in a way that lldb or others might...

On 7/9/2014 6:51 AM, Charles Lepple wrote: > On Jul 9, 2014, at 6:31 AM, Eric S. Raymond<esr at thyrsus.com> wrote: > >> What I'd like to do is this: confer in real-time, perhaps via IRC, >> with someone who knows this process. Ask about every step >> (thought processes and diagnostics). *Write them down* and turn >> this into a document on how to qualify

...ed in the first place. > > > > > >> Anyways, there seem to be a few, all somewhat bad options left to us > with ASan/TSan and similar more "advanced" runtimes: > >> > >> 1) Swallow the lame binary attribution clause requirement. Document > this noisily. > >> 2) Require they are build as DSOs, and thus the attribution restricted > to that runtime library entity. > > > > Maybe 2a: engineer asan so that it *optionally* links to the DSO. If > the DSO is present, functionality is enabled, if not, it is silently > disable...

I was told that my earlier submission of this report contained a user-hostile attachment (courtesy of Outlook), so here it is again, with the log included below. The problem: Files that exist only on the remote system are deleted silently (i.e. not logged), rather than noisily as implied by the recommendation of --dry-run in the rsync man page definition of --delete to see what would be deleted. I am intending to use rsync to replace rdist in an disaster recovery suite for several major banks and need to be able to provide the same details of what files were deleted as a...

Earlier today I added this feature: http://git.et.redhat.com/?p=libguestfs.git;a=commitdiff;h=34d2df41626f1ee4172a6d40b06d72d6ed9d6348 Unfortunately this feature doesn't work out. I forgot about kernel modules, which are contained in the initramfs, and stop working noisily if you just try to change the kernel. So I'm going to revert this patch, and perhaps think of some other way to do it later. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 75 OCaml...

...k when the dual licensing happened in the first place. > > >> Anyways, there seem to be a few, all somewhat bad options left to us with ASan/TSan and similar more "advanced" runtimes: >> >> 1) Swallow the lame binary attribution clause requirement. Document this noisily. >> 2) Require they are build as DSOs, and thus the attribution restricted to that runtime library entity. > > Maybe 2a: engineer asan so that it *optionally* links to the DSO. If the DSO is present, functionality is enabled, if not, it is silently disabled and the app still works (at...