Displaying 20 results from an estimated 120 matches for "sways".
Did you mean:
says
2008 May 15
0
"ServerAliveInterval" and "ServerAliveCountMax" doesnt work in openssh50?
Hi OpenSSH team,
We found that openssh5.0 has a bug with the "ServerAliveInterval" and "ServerAliveCountMax" options.
This function doesnt work at all, which means when the Maxtime reached, the ssh will not kill the connection and prompt the infomation "Connection Timedout" as it used to do.
We built the openssh5.0p1 code on the a Linux box, and use the
2008 May 15
1
"possible hijacking of X11-forwarded connections" bug has not been fixed completely
leanneHi OpenSSH team,
I am still able to reproduce this problem with openssh50 code both on hpux.
Seems like OpenSSH didn't fix this problem completely.
how to reproduce:
1. root at sshpa4# uname -aHP-UX sshpa4 B.11.23 U 9000/800 3267743753 unlimited-user license
2. sshd_config
X11Forwarding yesX11DisplayOffset 10X11UseLocalhost no // must not use "yes" to bind
2005 Nov 17
6
apache refuses to start because of port conflict
Here is the deal. I''m trying out the latest Instant Rails and when I
start it Apache claims that the web port is being used.
"Apache cannot be runned : another Web server use the Web port"
Okay, no problem. I went into the Apache configuration and changed the
port it was binding to. However I get the same problem.
The troubleshooting continues, so I install Apache by itself
2008 May 16
4
[Bug 1464] New: "possible hijacking of X11-forwarded connections" bug has not been fixed completely
https://bugzilla.mindrot.org/show_bug.cgi?id=1464
Summary: "possible hijacking of X11-forwarded connections" bug
has not been fixed completely
Classification: Unclassified
Product: Portable OpenSSH
Version: 5.0p1
Platform: Other
OS/Version: HP-UX
Status: NEW
Severity: security
2020 Jan 16
3
Re: libvirt-python: issue on fedora
On Wed, Jan 15, 2020 at 07:04:06PM +0100, Matthias Tafelmeier wrote:
>
> Hello,
>
> ran into oddish glitch on fedora 30 cloud image with tooling based on
> libvirt-python onpython3.7. *qemu-img *is installed though. Could anyone
> have a look.
I don't see qemu-img installed there. You've requested 'qemu-kvm' and
'qemu-system-x86' which provide the
2009 Oct 17
0
[LLVMdev] [cfe-dev] Developer meeting videos up
On Oct 17, 2009, at 1:32 AM, Owen Anderson wrote:
> Chris,
>
> On Oct 15, 2009, at 8:45 AM, Chris Lattner wrote:
>> Unfortunately, we found out at the last minute that Apple has a rule
>> which prevents its engineers from giving video taped talks or
>> distributing slides. We will hold onto the video and slide assets in
>> case this rule changes in the future.
2014 Sep 15
2
[LLVMdev] [PATCH][RFC]: Add fmin/fmax intrinsics
Given IEEE-754's sway, and its saying what it does on this point, but given
also the popularity of NaN-propagating min and max, how about a compromise?
We add intrinsics following the IEEE-754 semantics, but we also follow
IEEE-754 (and ARMv8) in renaming them to minnum and maxnum, to clarify
which interpretation these intrinsics are using.
-------------- next part --------------
An HTML
2009 Oct 17
5
[LLVMdev] [cfe-dev] Developer meeting videos up
Chris,
On Oct 15, 2009, at 8:45 AM, Chris Lattner wrote:
> Unfortunately, we found out at the last minute that Apple has a rule
> which prevents its engineers from giving video taped talks or
> distributing slides. We will hold onto the video and slide assets in
> case this rule changes in the future.
While I'm glad to know we all share similar sentiments on this, lots
of
2014 Sep 17
4
[LLVMdev] [PATCH][RFC]: Add fmin/fmax intrinsics
On Sep 15, 2014, at 4:17 PM, Owen Anderson <resistor at mac.com> wrote:
> I’d be fine with that proposal. I could even be convinced if we wanted to add a pair of NaN-propagating intrinsics as well, for targets and languages that want those semantics, even if I disagree with them. I do think that, if we are using the minnum/maxnum names, we should explicitly note that they are
2006 Oct 02
6
Calling All FS Fanatics
Now that I've been enlightened to the terrible write performance of ext3 on my
new 3Ware RAID 5 array, I'm stuck choosing an alternative filesystem. I
benchmarked XFS, JFS, ReiserFS and ext3 and they came back in that order from
best to worst performer.
I'm leaning towards XFS because of performance and because centosplus makes
kernel modules available for the stock kernel.
2018 May 30
0
Evaluation failure of IAPWS95 functions in a rowwise manner (tidyverse style)
Hi Shawn,
I don't think it has anything to do with the tidyverse. If you keep
simplifying your example you'll get all the way down to
> DTp(T=c(279,294),p=c(0.46,0.46))
[1] 1000.12283
--Ista
On Wed, May 30, 2018 at 2:14 PM, Shawn Way <SWay at meco.com> wrote:
> I'm trying to use the IAPWS95 package with the tidyverse packages. For some reason, the function is not
2018 May 30
2
Evaluation failure of IAPWS95 functions in a rowwise manner (tidyverse style)
I'm trying to use the IAPWS95 package with the tidyverse packages. For some reason, the function is not outputting the correct rho.
A minimal example with results is below. I've also included the definition of the DTp function from the IAPWS95 library.
====================================
library(IAPWS95)
library(tidyverse)
initial <- data.frame(T=c(279,294),p=c(0.46,0.46))
2015 May 19
3
Turning off wifi in CentOS 7
On 5/19/2015 10:24 AM, James Hogarth wrote:
> On 19 May 2015 11:40, <me at tdiehl.org> wrote:
>>
>>
>> Or if you want a bigger hammer:
>>
>> systemctl disable NetworkManager.service
>> systemctl enable network.service
>> systemctl stop NetworkManager.service
>> systemctl start network.service
>>
>> The above will disable
2021 Sep 27
1
回复: What types of volumes are supported in the latest version of Gluster?
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20210927/9d027096/attachment.html>
2003 Sep 17
0
FW: opiekey segfault ... isn't that harmfull? it's setuid root
Hi,
I dunno much about exploiting, but I was wondering about the setuid root
program 'opiepasswd' to use one-time-passwords.
When having a seed of (null) and a sequence of -1, I get a segfault.
Kernel/base:
FreeBSD lama.inet-solutions.be 4.8-RELEASE-p4 FreeBSD 4.8-RELEASE-p4 #0:
Sun Aug 31 21:00:38 CEST 2003
root@lama.inet-solutions.be:/usr/obj/usr/src/sys/LAMA i386
Make.conf:
2004 Feb 04
5
Date Time Conversion problems...
At one time (version 1.7), the code below used to work for converting and
extracting based on the Date Time. In version 1.8.1, something changed I
know, but I cannot for the life of me figure out what...
Data:
UserName,RequestDate,PO,OrderDate,ExpDelivDate,Vendor,Total
"Woody, Jim",12/19/2002,AP15063,1/7/2003,2/10/2003,Ames ,8570
"Harrold,
2006 Nov 04
0
rake db:migrate is semi-broken
Whenever I run rake db:migrate I get the following "error":
antrover:~/Sway/Projects/mi7/branches/sway_dev_mi7 dhoefler$ rake db:migrate
(in /Users/dhoefler/Sway/Projects/mi7/branches/sway_dev_mi7)
/usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/validations.rb:334:
warning: `*'' interpreted as argument prefix
2020 Jul 30
2
[PATCH v3] drm/nouveau: Accept 'legacy' format modifiers
Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK()
family of modifiers to handle broken userspace
Xorg modesetting and Mesa drivers. Existing Mesa
drivers are still aware of only these older
format modifiers which do not differentiate
between different variations of the block linear
layout. When the format modifier support flag was
flipped in the nouveau kernel driver, the X.org
modesetting driver
2020 Jul 27
2
[PATCH v2] drm/nouveau: Accept 'legacy' format modifiers
On 7/23/20 9:06 PM, Ben Skeggs wrote:
> On Sat, 18 Jul 2020 at 13:34, James Jones <jajones at nvidia.com> wrote:
>>
>> Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK()
>> family of modifiers to handle broken userspace
>> Xorg modesetting and Mesa drivers. Existing Mesa
>> drivers are still aware of only these older
>> format modifiers which do not
2020 Jul 18
2
[PATCH v2] drm/nouveau: Accept 'legacy' format modifiers
Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK()
family of modifiers to handle broken userspace
Xorg modesetting and Mesa drivers. Existing Mesa
drivers are still aware of only these older
format modifiers which do not differentiate
between different variations of the block linear
layout. When the format modifier support flag was
flipped in the nouveau kernel driver, the X.org
modesetting driver