similar to: [Bug 3784] New: Support building OpenSSH with AWS-LC

https://bugzilla.mindrot.org/show_bug.cgi?id=3740 Bug ID: 3740 Summary: Tracking bug for OpenSSH 10.0 Product: Portable OpenSSH Version: -current Hardware: Other OS: Linux Status: NEW Keywords: meta Severity: enhancement Priority: P5 Component: Miscellaneous

Dear R-Users I have created the following table in R: Year TACC.SNA1 Catch.SNA1 TACC.SNA2 Catch.SNA2 TACC.SNA3 Catch.SNA3 111 1985-86 9396 18595 1860 530 1486 16727 112 1986-87 3155 12195 9506 7067 4991 2300 113 1987-88 6913 2074 3740

I hope you'll all forgive me for displaying my severe lack of knowledge on this topic, and I can't really provide much in the way of reproducible code. A colleague of mine has asked if I know how to import an S object into R. The object is stored in a file named 'pre3.f' When I open the file as a text document I get what's printed below. Being one of those young bucks with

https://bugzilla.samba.org/show_bug.cgi?id=3784 Summary: Showing Progress without being Verbose Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: Tam@SiuLung.com

I'm just in the process of upgrading from nut-2.4.1 to 2.4.3 on a dual-Xeon box running Solaris 10 amd64 (i686-pc-solaris2.10). I configured as follows: ./configure --prefix=/opt/nut --with-gnu-ld --with-serial --without-usb --with-cgi --with-gd-includes=-I/usr/local/include --with-gd-libs="-L/usr/local/lib -R/usr/local/lib -lgd" --with-user=nut --with-group=nut

This is not a NUT question per se ... or at least, I don't think it is. I just replaced the battery pack in my HP R3000XR; the new batteries were shipped with 90% charge, were at about 87% when they went in, and were up to 98% charge the next day. Last weekend, the server that runs NUT went down for no apparent reason, wiping out its boot blocks, corrupting its boot archive beyond

Hi, I have a S4 based package package that was loading fine on R 2.5.0 on both OS X and Linux. I was checking the package against 2.5.1 and doing R CMD check does not give any warnings. So I next built the package and installed it. Though the package installed fine I noticed the following message: Loading required package: methods Error in loadNamespace(package, c(which.lib.loc, lib.loc),

Greetings, I've just installed nut-2.4.1 on a Solaris 10 x86 machine to monitor a HP R3000XR UPS. SunOS babylon4 5.10 Generic_138889-08 i86pc i386 i86pc Solaris First of all, I encountered a single problem during the build. After configuring, drivers/Makefile ends up containing the following line: LIBNETSNMP_LDFLAGS = -R../lib -L/usr/sfw/lib -lnetsnmp -lgen [...] This is clearly

I seem to have NUT all working with my R3000XR, except for the CGIs. The webserver's all properly configured and upsstats.cgi *runs*, but doesn't yield any useful output - no values are displayed, every value is replaced by [error: Invalid argument]. Apache is not logging any resulting errors, and there doesn't seem to be a lot of useful documentation on the CGIs to troubleshoot

I posted earlier about a problem with a HP R3000XR that was showing abnormally low charge a couple of days after replacing the battery pack. For those with R3000XRs, the progblem seems to be: (1) while you CAN hot-swap the battery-pack on an R3000XR, the UPS automatically goes into bypass mode when you do so; (2) it doesn't necessarily come OUT of bypass mode after you install the

On the basis of continuing experience, one final piece of R3000XR battery pack advice: After swapping the R3000XR battery pack, power-cycle the UPS, wait until the battery pack is at least 50% charged, then disconnect the UPS from wall power for a minute or so before plugging it back in. Until I did this, my UPS would charge the battery pack fully, then let it slowly self-discharge. After

On Fri, Feb 04, 2011 at 12:26:08PM +1100, Damien Miller wrote: > OpenSSH 5.8 has just been released. It will be available from the > mirrors listed at http://www.openssh.com/ shortly. I seem to have found a bug in 5.8p1. I work remotely, and use three SSH tunnels, two of the form ssh -L port:host:destport -f -N -q -l remoteuser remotehost, and one of the form ssh -D port -f -C -q -N -l

On Fri, Feb 14, 2003 at 12:44:50AM -0800, Kris Kennaway wrote: > On Sat, Jan 18, 2003 at 05:50:05PM -0500, Tim Vanderhoek wrote: > > On Sat, Jan 18, 2003 at 10:38:27PM +0100, Gunnar Flygt wrote: > > > > > > Actually it seems more that some of the pors have huge "include's" > > > as /usr/ports/devel/cdk as it includes the big maninfo.mk, or >

The scenario: I have two Samba servers on my network. One, running v3.0.37, is on my main server, a Solaris 10 x86 box. The other, just updated from 3.0.37 to 3.4.5 in the hope of solving this problem, is on my workstation, a Gentoo Linux box. The Linux Samba server shares only [homes]. The Solaris Samba server shares [homes] and four other shares. Unix UIDs are synchromized betwene the

I tried to establish connection to my aws s3 account like this in my irb console - AWS::S3::Base.establish_connection!(:access_key_id => ''my access key'', :secret_access_key => ''my secret key'', :server => " s3-ap-southeast-1.amazonaws.com") And it works well and prompt this - => #<AWS::S3::Connection:0x8cd86d0

This is an automated email from the git hooks/post-receive script. arrfab pushed a commit to branch master in repository centos/centos.org. The following commit(s) were added to refs/heads/master by this push: new 973d90a Added AWS as sponsor 973d90a is described below commit 973d90a1c09ad0ef6efdf200cc0e102f75442448 Author: Fabian Arrotin <arrfab at centos.org> AuthorDate: Tue Dec 3

Hello all, and thank you very much for the Centos 7 HVM AMI [1], greatly appreciated! This AMI does not work on the newly launched AWS Frankfurt region (eu-central-1). Any plans for fixing that? According to the AWS announcement [2], "The Region supports all sizes of T2, M3, C3, R3, and I2 instances". (We'll be running the CentOS 7 HVM AMI going forward, but looks like none of

On 04/12/2016 01:37 PM, Peter Steele wrote: > On 04/11/2016 11:33 AM, Laine Stump wrote: I wouldn't be too quick to > judgement. First take a look at tcpdump on the bridge interface that > the containers are attached to, and on the ethernet device that > connects the bridge to the rest of Amazon's infrastructure. If you see > packets from the container's IP going out

On 07/26/2017 09:29 AM, Stephan Koledin wrote: > Some additional info... > > AFAIK, the AMIs I'm referring to are owned/maintained by the CentOS > team, not by AWS. Details and suggestions to contact this list for > assistance are published at both https://wiki.centos.org/Cloud/AWS and > https://wiki.centos.org/Cloud/AWS > > Basically, the maintainer of the Centos.org

Some additional info... AFAIK, the AMIs I'm referring to are owned/maintained by the CentOS team, not by AWS. Details and suggestions to contact this list for assistance are published at both https://wiki.centos.org/Cloud/AWS and https://wiki.centos.org/Cloud/AWS Basically, the maintainer of the Centos.org AWS account just needs to add/approve the current AMIs for the g3.* instance