Displaying 4 results from an estimated 4 matches for "filternam".
Did you mean:
filtername
1997 Oct 31
0
postscript printing on W95 client
...the configuration files
2) install ghostscript, portable bitmap utils etc
3) install 'Magicfilter', it may need all of '2)'
4) modify the (last) lines in 'smbprint' to something like:
(
# comment
echo "print -"
cat
) | /usr/spool/lpd/<printername>/<filtername> | /usr/local/bin/smbclient
"\\\\$server\\$service" $password -U $server -N -P >>$logile
The last two form one *long* line. Printername is the name from
printcap, filtername is the filter applicable for the printer
connected to the WIN95 box.
Kees
2019 Sep 20
4
Re: [PATCH v4 07/12] v2v: nbdkit: Add the readahead filter unconditionally if it is available.
On Fri, Sep 20, 2019 at 10:28:18AM +0100, Richard W.M. Jones wrote:
>The readahead filter is a self-configuring filter that makes
>sequential reads faster when the plugin is slow (and all of the
>plugins we use here are always slow).
>
>I observed the behaviour of the readahead filter with our qcow2
>overlay when converting a guest from a vCenter source. Even when
>doing
2019 Sep 20
0
Re: [PATCH v4 07/12] v2v: nbdkit: Add the readahead filter unconditionally if it is available.
...ends.
-
plugin: null
(/usr/lib64/nbdkit/plugins/nbdkit-null-plugin.so)
size=<SIZE> Size of the backing disk
So we could probably improve --dump-plugin to ALSO show details about
the filter (such as a second path=), the way --help does, or even add a
'nbdkit --dump-filter filtername' to work in isolation. But while you'd
have to wait for a future nbdkit release to get more details from
--dump-plugin, and/or a way to list all available filters (think search
permissions on a directory), you already have a way with current nbdkit
to check existence of a filter (think re...
2010 Jun 30
0
FYI: a short guide to libvirt & network filtering iptables/ebtables use
...clean-traffic'. This pulls together all the building blocks
into one filter that you can then associate with a guest NIC.
This stops the most common bad things a guest might try, IP
spoofing, arp spoofing and MAC spoofing. To look at the rules for
any of these just do
virsh nwfilter-dumpxml FILTERNAME|UUID
They are all stored in /etc/libvirt/nwfilter, but don't edit
files there directly. Use 'virsh nwfilter-define' to update
them. This ensures the guests have their iptables/ebtables
rules recreated.
To associate the clean-trafffic filter with a guest, edit the
guest XML config and...