search for: lumpy

I was wondering whether there is unbearable overhead involved in breaking css into multiple stylesheets? I''m running lighttpd, and the following article discusses why one might want to do that: http://justinfrench.com/?id=141 My CSS is beginning to get a bit lumpy to digest in one glance and the article(s) seem to make a cogent argument for separating functional elements out. I just wanted to make sure there weren''t any Rails or server issues that would be problematic. TIA -- View this message in context: http://www.nabble.com/-OT-Serving-Multiple-...

...======== FreeBSD-SA-02:27.rc Security Advisory The FreeBSD Project Topic: rc uses file globbing dangerously Category: core Module: rc Announced: XXXX-XX-XX Credits: lumpy <lumpy@the.whole.net> Affects: FreeBSD 4.4-RELEASE FreeBSD 4.5-RELEASE FreeBSD 4-STABLE prior to the correction date Corrected: 2002-05-09 17:39:01 UTC (RELENG_4) 2002-05-09 17:40:27 UTC (RELENG_4_5) 2002-05-09 17:41:...

...lter should handle ENOSPC errors automatically by > reclaiming blocks from the cache > > +nbdkit-rate-filter: > + > +* allow other kinds of traffic shaping such as VBR > + > +* limit traffic per client (ie. per IP address) > + > +* split large requests to avoid long, lumpy sleeps when request size > + is much larger than rate limit Can't you pair the blocksize filter in front of this one to accomplish that already? -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org

Hi, Working on a report that is going to have a large number of graphs and summaries. We have 80 "groups" with 20 variables each. Ideally, I'd like to produce ONE page for each group. It would have two columns of 10 graphs and then the 5 number summary of the variables at the bottom. So, perhaps the top 2/3 of the page has the graphs and the bottom third has 20 rows of data

...or = suser(p->p_ucred, &p->p_acflag)) != 0)) + return (error); LEASE_CHECK(vp, p, p->p_ucred, LEASE_WRITE); VOP_LOCK(vp); VATTR_NULL(&vattr); VI. Credits Theo de Raadt came up with the firewalling solution presented here. lumpy@blue.9mm.com brought this problem to light. ============================================================================= FreeBSD, Inc. Web Site: http://www.freebsd.org/ Confidential contacts: security-officer@freebsd.org Security notifications: security-not...

For virt-v2v we have been discussing how to limit network bandwidth. The initial discussion has been around how to use cgroups to do this limiting, and that is still probably what we will go with in the end. However this patch gives us another possibility for certain virt-v2v inputs, especially VDDK. We could apply a filter on top of the nbdkit plugin which limits the rate at which it copies

...d | 1 + plugins/ssh/nbdkit-ssh-plugin.pod | 1 + plugins/vddk/nbdkit-vddk-plugin.pod | 2 + 9 files changed, 486 insertions(+) diff --git a/TODO b/TODO index d2cf0ae..02a095e 100644 --- a/TODO +++ b/TODO @@ -136,6 +136,12 @@ nbdkit-rate-filter: * split large requests to avoid long, lumpy sleeps when request size is much larger than rate limit +nbdkit-retry-filter: + +* allow user to specify which errors cause a retry and which ones are + passed through; for example there's probably no point retrying on + ENOMEM + Filters for security -------------------- diff --git a...

The following is a patch I've been working on to support a "ChrootUser" option in the sshd_config file. I was looking for a way to offer sftp access and at the same time restict interactive shell access. This patch is a necessary first step (IMO). It applies clean with 'patch -l'. Also attached is a shell script that helps to build a chrooted home dir on a RedHat 7.2

...| 1 + plugins/vddk/nbdkit-vddk-plugin.pod | 2 + server/backend.c | 8 + 10 files changed, 489 insertions(+) diff --git a/TODO b/TODO index d2cf0ae..02a095e 100644 --- a/TODO +++ b/TODO @@ -136,6 +136,12 @@ nbdkit-rate-filter: * split large requests to avoid long, lumpy sleeps when request size is much larger than rate limit +nbdkit-retry-filter: + +* allow user to specify which errors cause a retry and which ones are + passed through; for example there's probably no point retrying on + ENOMEM + Filters for security -------------------- diff --git a...

...@@ Suggestions for filters * nbdkit-cache-filter should handle ENOSPC errors automatically by reclaiming blocks from the cache +nbdkit-rate-filter: + +* allow other kinds of traffic shaping such as VBR + +* limit traffic per client (ie. per IP address) + +* split large requests to avoid long, lumpy sleeps when request size + is much larger than rate limit + Filters for security -------------------- diff --git a/filters/rate/Makefile.am b/filters/rate/Makefile.am new file mode 100644 index 0000000..c39aa01 --- /dev/null +++ b/filters/rate/Makefile.am @@ -0,0 +1,64 @@ +# nbdkit +# Copyrigh...

hello list (and martin) ;x i have now composed my final(?) policy routing design. the goals i had when beginning with this, for you that have not follow mine and martins thread, was to 1) only let 192.168.1/24 to see all routes, 2) not route between defined networks, except to and from 192.168.1/24 and 3) not defined networks should only be able to reach 192.168.1/24. this might sound simple.

This is a retry filter implementation as outlined here: https://www.redhat.com/archives/libguestfs/2019-September/msg00167.html It is only lightly tested. One way to test it is to try an SSH copy (see the commit message for patch 2/2), and in the middle of the copy kill the per-connection sshd on the remote machine. You will see that the copy recovers after a few seconds. Add the nbdkit -v

v1 was here: https://www.redhat.com/archives/libguestfs/2019-September/msg00199.html v2: - Adds a fairly simple yet comprehensive test using sh plugin. - Rebase and retest. Patch 1 is a misc patch not really related to the series. Rich.

v2 was here: https://www.redhat.com/archives/libguestfs/2019-September/msg00221.html I think this is more like "the one". It handles reopen failing correctly, and there is a second test for that. I also ran my sshd tests locally and it worked in all scenarios I could think up (except of course sshd not being available at the start, but we want that to fail). Rich.

The file{} type can do all of the following: * manage single files * manage directories * manage symlinks * manage recursive file copies The intersection of all these bits of functionality makes it difficult to understand exactly what is going on when you''re new to Puppet, and even experienced users often don''t know how combining symlinks/content management is going to work.