users August 2016

users@lists.fedoraproject.org

135 participants
115 discussions

MEGA Invitation
by MEGA 02 Aug '16

02 Aug '16

d327roque(a)gmail.com sent you an invitation to join MEGA. --- Message from user: --- Hello, join me on MEGA and get access to encrypted storage and communication. Get 50 GB free! --- Please create your free MEGA account by clicking on the following link: https://mega.nz/#newsignupdXNlcnNAbGlzdHMuZmVkb3JhcHJvamVjdC5vcmdpzDqXVpXBUA Best regards, Team MEGA

1 0

gsl-1 and gsl-2
by Patrick Dupre 02 Aug '16

02 Aug '16

Hello, Is it possible to install gsl-1 and gsl-2 with fc24 ? Thank for your help =========================================================================== Patrick DUPRÉ | | email: pdupre(a)gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================

2 2

Simultaneous DHCP and static IP address with NetworkManager
by Clayton Louden 01 Aug '16

01 Aug '16

Hi, I've got a NIC that gets one address via dhcp and another one statically assigned. This is done with Fedora's legacy network service (systemctl start network) and these config files /etc/sysconfig/network-scripts/ifcfg-enp0s25: HWADDR=XX:XX:XX:XX:XX:XX TYPE=Ethernet BOOTPROTO=dhcp DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_PEERDNS=yes IPV6_PEERROUTES=yes IPV6_FAILURE_FATAL=no NAME=enp0s25 ONBOOT=yes and /etc/sysconfig/network-scripts/ifcfg-enp0s25:0: TYPE=Ethernet BOOTPROTO=none IPADDR=192.168.99.4 PREFIX=24 DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=no NAME=static-ip ONBOOT=yes which works just fine: # ip addr show ... 2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff inet 192.168.1.68/24 brd 192.168.1.255 scope global dynamic enp0s25 valid_lft 6887sec preferred_lft 6887sec inet 192.168.99.4/24 brd 192.168.99.255 scope global enp0s25:0 valid_lft forever preferred_lft forever inet6 fe80::2ad2:44ff:fe7d:c66d/64 scope link valid_lft forever preferred_lft forever How can I achieve the same with NetworkManager? If I just disable the legacy network service and start NetworkManager with the same set of config files, I'll just get an IP address from the dhcp server (it seems the ifcfg-enp0s25:0 file is simply ignored) Any pointers are greatly appreciated!

2 1

fedup F20 to F24
by JD 01 Aug '16

01 Aug '16

Is it advisable? What sort of problems could the user encounter? Reason for asking: Many locally compiled programs (non-fedora sources) that compile and build (via rpmbuild) just find under F20, but will not compile on another machine running F24 (too many dependencies). P.S: For fun, Just wondering about this: since OS can run both 64 and 32 bit apps (Installation is 64 bit), and the apps link with the libs in /usr/lib64 or /usr/lib; then, why not be able to build and run apps which require libs of older fedora releases? for example: have /f20/usr/lib and /f20/usr/lib64 on a system of higher or lower OS release version. Yes, it would requires a lot of disk space for all those libs of that specific release, but disk space is cheap and plenty. I hope some savvy and inspired developer(s) can pick up on this idea :) :) It would help keep any fedora machine up to snuff for multiple releases. Cheers! JD

1 0

Date change on reboot
by Stephen Davies 01 Aug '16

01 Aug '16

My F22 randomly crashes to a frozen state that requires a power cycle to restart. When this happens, the time stamp on log files such as /var/log/messages changes for a while before reverting to the correct date and time. Today,the sequence was: Jul 24 10:55:55 mustang rsyslogd: [origin software="rsyslogd" swVersion="8.8.0" x-pid="853" x-info="http://www.rsyslog.com"] start Jul 15 11:19:20 mustang systemd: Stopped target Default. Jul 15 11:19:25 mustang systemd: Stopping Default. followed by some 17,000 lines with Jul 15 through to: Jul 15 19:28:11 mustang named[1221]: client 122.61.143.143#39431 (isc.org): query (cache) 'isc.org/ANY/IN' denied Jul 24 10:56:14 mustang rsyslogd-2177: imjournal: begin to drop messages due to rate-limiting Sun Jul 24 10:56:16 ACST 2016 rc.fw Jul 24 11:06:11 mustang rsyslogd-2177: imjournal: 2971956 messages lost due to rate-limiting A similar thing happens in /var/log/secure (though with fewer Jul 15 entries). The Jul 15 dates have been appearing at/after the last two or three crashes. Even though the Jul 15 entries look to span over eight hours, the actual time span was only a minute or so. Any suggestions as to what is happening here? Cheers and thanks, Stephen

10 25