search for: knobs

Greetings, I'm a little curious about the way FORBIDDEN knob is used in ports system. Traditionally, we use it to mark a port which have known security issue, with the new vuxml mechanism, are we still doing the same thing when necessary? Or, only the "critical" ones, for example, remote exploitable buffer overruns, etc? If the second assumption (only critical ones are marked

...? > (insn-level metadata for vptr store and module-level metadata for DTORs) > > > Using instruction level metadata for this would be appropriate. However, > I also don't understand why a race on this is truly benign. I'm also > concerned that you're adding even more knobs to clang and IR for special > case situations. > As for "more knobs", Chandler mentioned to me recently that being able to identify vptr accesses will help virtual function call inlining, so we may still need this knob for other purposes. --kcc > How many more special cases...

I am using the script below to simulate a very high bandwidth connection.I find that I could not turn the bandwidth knob up to 100Mbit.I have had a look at this generally,but could not find an answer.any help would much appreciated as i have spent a lot of time on this and have not found any answers anywhere. In my test,I have four network cards and their rate are all 1000Mbps. my scripts:

...even if our request can be deemed undefined per NBD protocol). I'd like to change it so that by default, we reject as much as we can client-side for less traffic, but where the user can also change things on the fly for server-side integration testing. My remaining question, then, is how many knobs to expose initially? As written, I've only given two knobs, but make the case in each patch how it could easily be split into four knobs if we think the finer granularity is worthwhile. A future knob for block-size validation would also make sense, especially given the recent addition of suppo...

Hi, I'm working on a patch to overhaul docs+doxygen builds for both llvm and clang source trees. Here's a sample of what it looks like for class clang::driver::Action (sorry, llvm API docs are a bigger set so only clang has been posted at this free webhost). Basically the output is a bump to latest doxygen plus custom css; the wins (IMHO) are the new style doesn't waste so much

Excellent work, this greatly improves the clarity of the generated docs. I would love it if the inheritance diagrams were kept as they are and the collaboration diagrams were hidden under a knob. Thanks, John On Fri, Apr 30, 2010 at 8:54 AM, mike-m <mikem.llvm at gmail.com> wrote: > Hi, I'm working on a patch to overhaul docs+doxygen builds for both llvm > and clang source

It looks like someone pooched a domain transfer, and the whois entry for centos.org is missing its NS records. I've sent an email to the whois tech contact @redhat, but I'm sending this to the list to hopefully bring it to someone else's attention, as well. Hopefully it gets gets out before my mailserver expires its DNS cache for centos.org. Expect centos.org to be offline for a bit

> No comments? Mostly no. There are no presets because the encoder is smart enough to act intelligently by default. The exposed knobs are exposed only for those who know they actually need them. This is pretty much how Xiph encoders have always been. The programming API is a bit different, because there are more use cases for streaming. Monty

Hi! There are configuration knobs (TCPKeepAlive) to enable/disable the use of TCP keepalives both in the ssh client and server. Unfortunately some UNIX systems default to SO_KEEPALIVE=on and some to =off. This may even be settable on a per host basis (OpenBSD default net.inet.tcp.always_keepalive=1 ???). For the TCPKeepAlive confi...

...or message is "failed to map segment from shared object? ? no additional information. Cryptic error messages like this have the odour of imposed resource restrictions, so I?m wondering if there are any on the pipe/filter/execute implementation (e.g. via program_client_run). Any configuration knobs I can twiddle? Any insights for debugging? PS this is the dovecot 2.2.22 (fe789d2), the one that ships with Ubuntu Xenial. Regards, -- Dorian Taylor Make things. Make sense. https://doriantaylor.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.as...

...hese flags should only be used by people looking at code. For example, if a pass has a hidden option that controls some knob, you should only find out about it by reading the code. We don't want people surfing through all the hidden options to "see what is available". What specific knobs are you interested in? Maybe they shouldn't be hidden. -Chris > > Any idea? Thanks! > > > [1] http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-October/044484.html > [2] http://comments.gmane.org/gmane.comp.compilers.llvm.cvs/101547 > [3] http://lists.cs.uiuc.edu/piper...

Hi, I've a broken IMAP server, which doesn't support pipelining and fails on dovecot's attempt to do this ([C] is dovecot's imapc, [S] is the IMAP server): [C] 24 LOGIN "user" "pass" [S] 23 OK [C] 25 SELECT "INBOX" [C] 23 UID FETCH 2 (INTERNALDATE) [S] 25 OK [S] 23 BAD No mailbox selected Sadly, fixing the server would be a hard task, turning off

Hi, There's a hardcoded reference to /usr/lib/libkrb.a in Makefile.inc. Is there a special reason, that there's no knob but a file check? AFAIK - my /usr/lib/libkrb.a stems from the 4.2-RELEASE cd install I started this comp with (it's dated Nov 2000) and thus hasn't been updated since and any linkage with it, results in undefined des(3) references. Since sysutils/libchk

I try to compile port lang/ruby19 and I always get on a FreeBSD 9.1-STABLE box the following error message, which is obviously triggered by some port auditing - but I do not find the "knob" to switch it off. Can someone give a hint, please? Regards, Oliver ===> Cleaning for ruby-1.9.3.392,1 ===> ruby-1.9.3.392,1 has known vulnerabilities: ruby-1.9.3.392,1 is vulnerable: Ruby

...is already one: needSet / *AbsoluteOffsets etc). Also "generic" function for emission of data in specified format should be written (it should take care about decoration also). This will allow to describe target-specific stuff in one place instead of introducing / tweaking bunch of magic knobs. Comments? Ideas? -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

...ose be a right solution? > (insn-level metadata for vptr store and module-level metadata for DTORs) Using instruction level metadata for this would be appropriate. However, I also don't understand why a race on this is truly benign. I'm also concerned that you're adding even more knobs to clang and IR for special case situations. How many more special cases like this are you going to require? -Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120319/b6d399c0/attachment.html>

Howdie, Is there a way to get the default BSD 5.3 openssh to compile against the MIT kerberos libraries? I have set NO_KERBEROS=yes in /etc/make.conf so that the heimdal kerberos is not built, and rebuilt world, then installed /usr/ports/security/krb5 and rebuilt world again. sshd is however not being built against MIT at all. [root@foobar] ~ # ldd /usr/sbin/sshd /usr/sbin/sshd:

Hello, Does the -fstack-protector option work on CLANG 3.1 and 3.2? There is thread on FreeBSD forums about the stack protector and ports and I'm wondering if it's possible to use the -fstack-protector option with CLANG. http://forums.freebsd.org/showthread.php?t=36927 -Kimmo

>> I found that scsicmd can't pass all the scsi3_test but the result of >> sg_inq is the same as it in the host. >> >> I am absolutely confused about this situation. Am I missed some >> information about it? I guess this is caused by the lack of capability. Please check if enough capability was added to kvm process by the following steps. 1. Check the pid of

On 09/08/2017 01:53 PM, Aki Tuomi wrote: > > On 08.09.2017 14:50, Nagy, Attila wrote: >> Hi, >> >> I've a broken IMAP server, which doesn't support pipelining and fails >> on dovecot's attempt to do this ([C] is dovecot's imapc, [S] is the >> IMAP server): >> >> [C] 24 LOGIN "user" "pass" >> [S] 23 OK