Failed installation of update testing of apcupsd
## apcupsd.conf v1.1 ## # # for apcupsd release 3.14.11 (31 January 2014) - redhat # # apcupsd POSIX config file # # = General configuration parameters # # UPSNAME xxx # Use this to give your UPS a name in log files and such. This # is particulary useful if you have multiple UPSes. This does not # set the EEPROM. It should be 8 characters or less. #UPSNAME # UPSCABLE cable # Defines the type of cable connecting the UPS to your computer. # # Possible generic choices for cable are: # simple, smart, ether, usb # # Or a specific cable model number may be used: # 940-0119A, 940-0127A, 940-0128A, 940-0020B, # 940-0020C, 940-0023A, 940-0024B, 940-0024C, # 940-1524C, 940-0024G, 940-0095A, 940-0095B, # 940-0095C, 940-0625A, M-04-02-2000 # UPSCABLE usb # To get apcupsd to work, in addition to defining the cable # above, you must also define a UPSTYPE, which corresponds to # the type of UPS you have (see the Description for more details). # You must also specify a DEVICE, sometimes referred to as a port. # For USB UPSes, please leave the DEVICE directive blank. For # other UPS types, you must specify an appropriate port or address. # # UPSTYPE DEVICE Description # apcsmart /dev/tty** Newer serial character device, appropriate for #SmartUPS models using a serial cable (not USB). # # usb BLANK Most new UPSes are USB. A blank DEVICE #setting enables autodetection, which is #the best choice for most installations. # # net hostname:portNetwork link to a master apcupsd through apcupsd's #Network Information Server. This is used if the #UPS powering your computer is connected to a #different computer for monitoring. # # snmp hostname:port:vendor:community #SNMP network link to an SNMP-enabled UPS device. #Hostname is the ip address or hostname of the UPS #on the network. Vendor can be can be APC or #APC_NOTRAP. APC_NOTRAP will disable SNMP trap #catching; you usually want APC. Port is usually #161. Community is usually private. # # netsnmp hostname:port:vendor:community #OBSOLETE #Same as SNMP above but requires use of the #net-snmp library. Unless you have a specific need #for this old driver, you should use 'snmp' instead. # # dumb /dev/tty** Old serial character device for use with #simple-signaling UPSes. # # pcnet ipaddr:username:passphrase:port #PowerChute Network Shutdown protocol which can be #used as an alternative to SNMP with the AP9617 #family of smart slot cards. ipaddr is the IP #address of the UPS management card. username and #passphrase are the credentials for which the card #has been configured. port is the port number on #which to listen for messages from the UPS, normally #3052. If this parameter is empty or missing, the #default of 3052 will be used. # # modbus/dev/tty** Serial device for use with newest SmartUPS models #supporting the MODBUS protocol. # UPSTYPE usb DEVICE # POLLTIME int # Interval (in seconds) at which apcupsd polls the UPS for status. This # setting applies both to directly-attached UPSes (UPSTYPE apcsmart, usb, # dumb) and networked UPSes (UPSTYPE net, snmp). Lowering this setting # will improve apcupsd's responsiveness to certain events at the cost of # higher CPU utilization. The default of 60 is appropriate for most # situations. #POLLTIME 60 # LOCKFILE path to lockfile # Path for device lock file. Not used on Win32. LOCKFILE /etc/apcupsd # SCRIPTDIR path to script directory # Directory in which apccontrol and event scripts are located. SCRIPTDIR /etc/apcupsd # PWRFAILDIR path to powerfail directory # Directory in which to write the powerfail flag file. This file # is created when apcupsd initiates a system shutdown and is # checked in the OS halt scripts to determine if a killpower # (turning off UPS output power) is required. PWRFAILDIR /etc/apcupsd # NOLOGINDIR path to nologin directory # Directory in which to write the nologin file. The existence # of this flag file tells the OS to disallow new logins. NOLOGINDIR /etc # # Configuration parameters used during power failures == # # The ONBATTERYDELAY is the time in seconds from
F20 and Rawhide: Headless install and enabling VNC
Hi, I'*m working on some PXE and kickstart stuff to install headless servers for F20 and Rawhide; did work so far. But is there any official way to enable VNC on a headless server ? I can ssh to this machines, but how do I access this machine via VNC ? I can enable VNC in the Gnome Control Center if I connect a monitor, but how do I enable this via ssh ? /etc/sysconfig/vncserver seems to be gone since F19 ? cu romal -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20 and Rawhide: Headless install and enabling VNC
I’m wondering about this myself. I use an F19 and F20 image, but I can’t get VNC to work on either. If anyone knows the trick, it would help me out as well. JC On Feb 20, 2014, at 4:13 PM, Robert M. Albrecht li...@romal.de wrote: Hi, I'*m working on some PXE and kickstart stuff to install headless servers for F20 and Rawhide; did work so far. But is there any official way to enable VNC on a headless server ? I can ssh to this machines, but how do I access this machine via VNC ? I can enable VNC in the Gnome Control Center if I connect a monitor, but how do I enable this via ssh ? /etc/sysconfig/vncserver seems to be gone since F19 ? cu romal -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Adventures with Rawhide
A few days ago I installed Rawhide from my local rsync. The Asmedia USB ports now work. The Display would not go above 1600 with the Nvidia gtx670 and Dell 30 incher. The rpmfusion xorg-x11-drv-nvidia did install and all was well. ... until the kernel was updated and now no X. So I re-installed rawhide and now the rpmfusion driver won't work. I really do miss running my 30 inch at full res. -- Chuck Forsberg WA7KGX c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc The High Reliability Software 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20 and Rawhide: Headless install and enabling VNC
On Thu, Feb 20, 2014 at 10:13:28PM +0100, Robert M. Albrecht wrote: But is there any official way to enable VNC on a headless server ? I can ssh to this machines, but how do I access this machine via VNC ? I can enable VNC in the Gnome Control Center if I connect a monitor, but how do I enable this via ssh ? If you install tigervnc-server it comes with /usr/lib/systemd/system/vncserver@.service This has a header comment which starts like that: # The vncserver service unit file # # Quick HowTo: # 1. Copy this file to /etc/systemd/system/vncserver@.service # 2. Edit USER and vncserver parameters appropriately # (runuser -l USER -c /usr/bin/vncserver %i -arg1 -arg2) # 3. Run `systemctl daemon-reload` # 4. Run `systemctl enable vncserver@:display.service` # . (and quite a bit more of relevant informations). I did not try that myself but I do not see why this should not work. /etc/sysconfig/vncserver seems to be gone since F19 ? Yeah; systemd actually allows to pass various configuration details via enviroment files but a general tendency and apparently heavily encouraged is to make this copy and edit. Personally I am finding that quite idiotic and detrimental to a long run maintenance. With an every update you should check now if something did not change you need to take care of. Multiply that by a number of such hand configured services and here you are. An alternative is configure such a thing once, forget it, and try to guess what is happening when in the future something goes screwy. Michal -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20 and Rawhide: Headless install and enabling VNC
On Thu, 2014-02-20 at 18:44 -0700, Michal Jaegermann wrote: On Thu, Feb 20, 2014 at 10:13:28PM +0100, Robert M. Albrecht wrote: But is there any official way to enable VNC on a headless server ? I can ssh to this machines, but how do I access this machine via VNC ? I can enable VNC in the Gnome Control Center if I connect a monitor, but how do I enable this via ssh ? If you install tigervnc-server it comes with /usr/lib/systemd/system/vncserver@.service This has a header comment which starts like that: # The vncserver service unit file # # Quick HowTo: # 1. Copy this file to /etc/systemd/system/vncserver@.service # 2. Edit USER and vncserver parameters appropriately # (runuser -l USER -c /usr/bin/vncserver %i -arg1 -arg2) # 3. Run `systemctl daemon-reload` # 4. Run `systemctl enable vncserver@:display.service` # . (and quite a bit more of relevant informations). I did not try that myself but I do not see why this should not work. /etc/sysconfig/vncserver seems to be gone since F19 ? Yeah; systemd actually allows to pass various configuration details via enviroment files but a general tendency and apparently heavily encouraged is to make this copy and edit. Personally I am finding that quite idiotic and detrimental to a long run maintenance. With an every update you should check now if something did not change you need to take care of. Multiply that by a number of such hand configured services and here you are. An alternative is configure such a thing once, forget it, and try to guess what is happening when in the future something goes screwy. The *point* of the copy-and-edit system is so the 'stock' configuration can be updated and you don't wind up with .rpmnews all over the place. If we ship it as /etc/systemd/system/vncserver@.service and you edit it, it's never going to be 'magically' reconciled on update, you'll just get a .rpmnew file. That's not any better. Things could still change behind your back and make your /etc/sysconfig file not work any more in the old system... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F20 and Rawhide: Headless install and enabling VNC
On Thu, Feb 20, 2014 at 10:51:42PM -0500, David wrote: Would this be of any use for you? 6.12. yum-plugin-merge-conf http://docs.fedoraproject.org/en-US/Fedora/14/html/Software_Management_Guide/ch06s12.html Sounds useful but not in the context we are talking about. I do not know if any of unit files in /usr/lib/systemd/system/ are config files, most likely not, and surely none of your modified copies will be recognized as such. This means that there will be nothing to merge. Michal -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
