Displaying 20 results from an estimated 206 matches for "settables".
Did you mean:
settable
2023 Jan 17
1
PR to test for users of Qx devices (blazer and nutdrv_qx)
Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>
>
> Cheers,
>
> One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279
>
> The gist of it is that "battery.voltage" and "battery.charge" were not always reported
2023 Jan 17
1
PR to test for users of Qx devices (blazer and nutdrv_qx)
Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>
>
> Cheers,
>
> One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279
>
> The gist of it is that "battery.voltage" and "battery.charge" were not always reported
2007 Nov 20
9
[Bug 13319] New: YV12 and YUY2 overlay broken on PPC with NV34M
http://bugs.freedesktop.org/show_bug.cgi?id=13319
Summary: YV12 and YUY2 overlay broken on PPC with NV34M
Product: xorg
Version: 7.3
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau at lists.freedesktop.org
2023 Jan 15
1
PR to test for users of Qx devices (blazer and nutdrv_qx)
Cheers,
One PR waiting to get into 2.8.1 release timeframe is
https://github.com/networkupstools/nut/pull/1652 stemming from issue
https://github.com/networkupstools/nut/issues/1279
The gist of it is that "battery.voltage" and "battery.charge" were not
always reported correctly with nutdrv-qx driver (might be handled better by
blazer drivers though), and the overrides
2004 Jul 05
1
printer preferences not settable using samba print driver
We're putting together a Linux-cups-samba print server for Windows
clients. A dozen print drivers have been loaded and used successfully on
the Windows clients from the samba server. But, one particular printer
is causing trouble: a Xerox DC 2240. When a windows client tries to open
the printer preferences, after connecting to the printer on the samba
print server, a popup says
2014 Aug 04
3
[Bug 82118] New: nouveau tearing with xvideo
https://bugs.freedesktop.org/show_bug.cgi?id=82118
Priority: medium
Bug ID: 82118
Assignee: nouveau at lists.freedesktop.org
Summary: nouveau tearing with xvideo
QA Contact: xorg-team at lists.x.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: lameventanas at gmail.com
2010 Feb 23
2
Feature Request: Settable 'nice' value.
So, some of us would like to be able to set the nice value on puppetd.
However, we don''t want all of our services (and some of our execs)
re-niced.
Would it be feasible/practical to have the ability to set the nice
value explicitly on Service and Exec calls?
Thanks,
Trevor
--
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvaughan@onyxpoint.com
-- This account not
2004 Jun 23
3
[PATCH] make pam service a settable option
This patch adds a config file option 'PAMService' that sets the PAM
service sshd will use. It should leave the current behavior unchanged if
PAMService is not set in the config file (i.e. use __progname for the
service or SSHD_PAM_SERVICE if it's set at compile time). The patch is
against the current portability release in CVS.
Why would you want something like this?
I have a machine
[virtio-dev] Re: [Qemu-devel] [PATCH] qemu: Introduce VIRTIO_NET_F_STANDBY feature bit to virtio_net
2018 Jun 15
2
[virtio-dev] Re: [Qemu-devel] [PATCH] qemu: Introduce VIRTIO_NET_F_STANDBY feature bit to virtio_net
On Fri, 15 Jun 2018 05:34:24 +0300
"Michael S. Tsirkin" <mst at redhat.com> wrote:
> On Thu, Jun 14, 2018 at 12:02:31PM +0200, Cornelia Huck wrote:
> > > > I am not all that familiar with how Qemu manages network devices. If we can
> > > > do all the
> > > > required management of the primary/standby devices within Qemu, that is
> >
2012 Feb 14
1
New variables?
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20120214/96cc8043/attachment.html>
2019 Dec 28
3
Settable minimum RSA key sizes on the client end for legacy devices.
Unix was not designed to stop you from doing stupid things, because that would also stop you from doing clever things.
- Doug Gwyn, in Introducing Regular Expressions (2012) by Michael Fitzgerald
Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: openssh-unix-dev <openssh-unix-dev-bounces+j.mccanta=f5.com at mindrot.org> on behalf of Steve Sether
2005 Aug 21
3
Icecast 2.3 RC1 Announcement
Ok folks, we are getting ready for version 2.3 of icecast and have built an
RC1 distribution. We encourage everyone to try out this new release and
provide us feedback. Please report all bugs to http://bugs.xiph.org
Here are the details :
Source Distribution:
http://downloads.xiph.org/releases/icecast/icecast-2.3.0.rc1.tar.gz
Source RPM:
2005 Aug 21
3
Icecast 2.3 RC1 Announcement
Ok folks, we are getting ready for version 2.3 of icecast and have built an
RC1 distribution. We encourage everyone to try out this new release and
provide us feedback. Please report all bugs to http://bugs.xiph.org
Here are the details :
Source Distribution:
http://downloads.xiph.org/releases/icecast/icecast-2.3.0.rc1.tar.gz
Source RPM:
2003 May 13
6
R crashes when resizing windows (PR#2992)
Full_Name: Gavin Alexander
Version: 1.7.0
OS: Win2000
Submission from: (NULL) (130.209.6.40)
When I resize the R-GUI console window by dragging an edge and drag for more
than a second or two, R crashes. The program exits, leaving a pop-up "Program
Error" box with the message:
"Rgui.exe has generated errors and will be closed by Windows.
You will need to restart the program.
An
2019 Dec 27
3
Settable minimum RSA key sizes on the client end for legacy devices.
> I fully agree with Steve here, and dislike developers' attitude of "We
> know what's good for you, and since you don't/can't have a clue - we
> won't trust you with decisions".
Well, I'm on the developers' side.
They need to produce a product that _now_ gets installed in some
embedded device and is expected to be still secure in 15 years and
longer
2010 Sep 09
2
plot symbol "+", but with variable bar lenghts
Hi,
does anybody know of some plotting function or an easy way to
generate "+" symbols with individually settable bar lengths?
I tried just combining "|" and "-" as pch and setting the size via cex,
but that doesn't really work since the two symbols have different default
lengths. Is there a horizontal | or a longer "-" available?
Thanks,
Rainer
2019 Dec 26
4
Settable minimum RSA key sizes on the client end for legacy devices.
Recently I tried to turn on SSH on my 12 year old APC-UPS.? I soon
discovered that I couldn't connect to it because my newer version of
openssh doesn't support RSA key sizes below 1024 bits.
I'd rather not dredge up a big fight, but I _would_ like to express a
desire for some form of overriding the minimum key size.? Basically I've
had to turn on telnet access again, lowering
2014 Jul 23
2
[LLVMdev] sys::path::system_temp_directory vs. sys::fs::createTemporaryFile
Hi, all. I noticed recently that llvm::sys::fs::createTemporaryFile does not use llvm::sys::path::system_temp_directory, instead relying on its platform-specific helper TempFile. Is there any reason for this disparity?
The two implementations are not in sync, either:
- TempDir honors TMPDIR, TMP, TEMP, TEMPDIR, and a configuration-settable P_tmpdir on Unix-y systems. system_temp_directory just
2007 Apr 17
5
How to change the default encoding for dynamic pages
Hello,
I''m trying to write a rails application serves by mongrel and using
accentuated characters in the .rhtml page. But Mongrel replace them by ''?'' .
It works fine for static pages by defining the charset to iso-8859-1 in the
mongrel_mime.yml
But how to change the default encoding (seems to be UTF-8) for the dynamic
pages ?
thanks for your help.
-------------- next
2011 Feb 04
1
read.csv trap
This is not specifically a bug, but an (implicitly/obscurely)
documented behavior of read.csv (or read.table with fill=TRUE) that can
be quite dangerous/confusing for users. I would love to hear some
discussion from other users and/or R-core about this ... As always, I
apologize if I have missed some obvious workaround or reason that this
is actually the desired behavior ...
In a nutshell,