search for: 400e

Displaying 9 results from an estimated 9 matches for "400e".

Did you mean: 400
2008 Jul 03
0
Cyberpower Value 600E UPS (unlisted) working
...and set it > up using NUT 2.2.x (on Gentoo x86_64). Everything is working great, > using the usbhid-ups driver, and the UPS isn't on the compatibility > lists, so I figured I'd post a little heads-up that it works. The > battery appears to be the main difference from the 400E and 800E > models, so I expect them to work as well. > I'm not sure that you're the right guy, I just took the address shown > to last modify the stable compatibility list. Feel free to direct me > to the mailing lists if necessary; I just didn't feel like signing up...
2015 Oct 13
1
Firewalld
...quot;eth0" HWADDR=52:54:00:76:0D:7F ONBOOT=yes UUID="8ab7ac2c-c089-4f9f-bb65-1abb781fe912" IPV6INIT=no BOOTPROTO=none TYPE=Ethernet IPADDR=96.92.106.4 PREFIX=29 GATEWAY=96.92.106.6 NOZEROCONF=yes and NAME="eth1" HWADDR=52:54:00:B3:03:66 ONBOOT=yes UUID="1d590cef-d5a2-400e-89e3-3c618f785c41" IPV6INIT=no BOOTPROTO=none TYPE=Ethernet IPADDR=192.168.6.222 PREFIX=24 DNS1=192.168.6.1 IPV4_FAILURE_FATAL=no NOZEROCONF=yes Emmett
2019 Nov 22
2
sendmail on Centos 7.7
On Fri, 2019-11-22 at 10:55 -0500, Stephen John Smoogen wrote: > [smooge at smoogen-laptop ~]$ host -t MX smtp-relay.gmail.com.com > smtp-relay.gmail.com.com mail is handled by 10 mx203.inbound-mx.org. > smtp-relay.gmail.com.com mail is handled by 10 mx203.inbound-mx.net. .w smtp-relay.gmail.com.com smtp-relay.gmail.com.com has address 79.124.78.105 smtp-relay.gmail.com.com has address
2019 Nov 22
0
sendmail on Centos 7.7
and, of course... $ host smtp-relay.gmail.com smtp-relay.gmail.com has address 74.125.142.28 smtp-relay.gmail.com has IPv6 address 2607:f8b0:400e:c08::1c $ whois 74.125.142.28 ... NetRange: 74.125.0.0 - 74.125.255.255 CIDR: 74.125.0.0/16 NetName: GOOGLE NetHandle: NET-74-125-0-0-1 Parent: NET74 (NET-74-0-0-0-0) NetType: Direct Allocation OriginAS: Organization: Google LLC (GOGL) RegDate: 2...
2015 Oct 13
2
Firewalld
On 10/12/2015 10:17 AM, Gordon Messmer wrote: > On 10/11/2015 03:00 PM, Emmett Culley wrote: >> I just noticed that when rebooting a CentOS 7 server the firewall comes back up with both interfaces set to REJECT, instead of the eth1 interface set to ACCEPT as defined in 'permanent' firewalld configuration files. > > Rather than paraphrasing, could you show the specific
2009 Jul 28
4
Patch for drivers.list
..."USB" "usbhid-ups" "Cyber Power Systems" "AE550" "USB" "usbhid-ups" +"Cyber Power Systems" "CP 1500C" "USB" "usbhid-ups" "Cyber Power Systems" "Value 400E" "USB" "usbhid-ups" "Cyber Power Systems" "Value 600E" "USB" "usbhid-ups" "Cyber Power Systems" "Value 800E" "USB" "usbhid-ups" root(upsmonitor)/usr/lo...
2012 Dec 27
4
Help Getting Postfix relaying via Gmail
...eanup[2603]: 8DEB1410B3: message-id=< 20121227101536.8DEB1410B3 at hbc.hillcrest.org.nz> Dec 27 23:15:36 hbc postfix/qmgr[2589]: 8DEB1410B3: from=< root at hbc.hillcrest.org.nz>, size=317, nrcpt=1 (queue active) Dec 27 23:15:37 hbc postfix/smtp[2605]: connect to smtp.gmail.com[2607:f8b0:400e:c00::6d]:587: Network is unreachable Dec 27 23:15:37 hbc postfix/smtp[2605]: vstream_buf_get_ready: fd 15 got 45 Dec 27 23:15:37 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.109]:587: 220 mx.google.com ESMTP vo8sm17581810pbc.16 Dec 27 23:15:37 hbc postfix/smtp[2605]: > smtp.gmail.com[1...
2010 Apr 16
0
Wine release 1.1.43
...nt icon. wordpad: Replaced program icon with a Tango compliant icon. taskmgr: Replaced program icon with a Tango compliant icon. Johan Gill (1): ddraw/tests: Added todo_wine test to verify resizing of fullscreen windows. J?rg H?hle (7): msvidc32: Fix "Unknown message: 400e". msacm32: Fix nesting in acmFilter/FormatTagEnum. winmm: MCI system commands are not eligible for auto-open. winmm: Improve MCI A/W mapping. msvidc: Fix 16bit VIDEO-1/CRAM decompression. winmm: Prepare transition of MCI parser to 64bit. winmm: MCI_SYSINFO d...
2018 Dec 20
5
Samba AD DC replication error - 2, 'WERR_BADFILE'
Hello everyone, I have setup two Samba AD DC's with BIND9_DLZ dns backend. faiserver.example.corp is one of them hosting all FSMO Roles. location-000001.example.corp is the second one. Both are in different subnets but can reach each other. Unfortunately replication only works from faiserver.example.corp -> location-000001.example.corp. In the other direction location-000001.example.corp