Discuss

discuss@lists.centos.org

2 participants
34758 discussions

C6.6 Gnome panel problem
by Fred Smith 27 Jul '15

27 Jul '15

Hi all! I usually keep the panels on my Centos 6.6 (Gnome) so they auto-hide, but t'other day I wanted to keep the top panel visible for a while to make the clock visible for doing some rough timings. so I open the top panel, click properties, and UNcheck the "autohide" checkbox, close the properties menu, and to my surprise, the panel still autohides. Went thru that exercise several times ("come on guys, lets keep doing the same thing over and over til it works!", like congress does) So I open up the gnome configuration editor and browse around to find apps/panel/default_setup/toplevels/top_panel and apps/panel/toplevels/top_panel. neither one has a check in the checkbox for autohide, so I'm at a loss here as to what's going on. Anybody out there got any clues? thanks! Fred -- ------------------------------------------------------------------------------- Under no circumstances will I ever purchase anything offered to me as the result of an unsolicited e-mail message. Nor will I forward chain letters, petitions, mass mailings, or virus warnings to large numbers of others. This is my contribution to the survival of the online community. --Roger Ebert, December, 1996 ----------------------------- The Boulder Pledge -----------------------------

3 2

CentOS-announce Digest, Vol 125, Issue 10
by centos-announce-request＠centos.org 27 Jul '15

27 Jul '15

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CentOS Continuous Release Repository updated with CentOS-6.7 RPMs (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 27 Jul 2015 06:44:32 -0500 From: Johnny Hughes <johnny(a)centos.org> To: CentOS-Announce <centos-announce(a)centos.org> Subject: [CentOS-announce] CentOS Continuous Release Repository updated with CentOS-6.7 RPMs Message-ID: <55B619A0.1090509(a)centos.org> Content-Type: text/plain; charset="utf-8" The packages that will become CentOS-6.7, as well as updates completed for CentOS-6.7 to date are now released into the CentOS-6.6 Continuous Release (CR) repository. All packages except for the centos-release RPM are included. The purpose of the CR repository is to make the built packages optionally available to users who opt in while we work on the CentOS-6.7 install tree and all the CentOS-6.7 install media and images. Normally the full release follows the CR release in 7-14 days if you do not use the CR process. For more info on the CR repository, see this link: http://wiki.centos.org/AdditionalResources/Repositories/CR If you want to enable CR on CentOS-6.6, use the command: yum install centos-release-cr You would then get the updates with the command: yum upgrade Users who choose to opt-in to this process can access the newly built packages, as soon as they are exported from the build system after some basic testing has been completed. They are less comprehensively reviewed in the QA validation stage than the full release (Note: "Less comprehensively" does not mean no QA testing ... it just means less than the full release). Some packages, like the anaconda installer, routinely receive updates during the full QA process, and the final versions may be updated from the CR version. Known issues: 1. sssd-common is no longer multilib in CentOS 6.7. If you have the 32bit sssd-common installed on your x86_64 system, you will need to remove it with yum remove sssd-common.i686 prior to updating. 2. The boost RPMs are built with cmake-2.8 and the configuration files produced cause issues building some source code. There are an upstream bugs here (which is likely NOT being fixed): https://bugzilla.redhat.com/show_bug.cgi?id=849791 https://bugzilla.redhat.com/show_bug.cgi?id=1245805 and there are related CentOS issues found previously: http://bugs.centos.org/view.php?id=8117 If you are using boost to create packages, you can use the switch: "-DBoost_NO_BOOST_CMAKE=ON" To build sources that exhibit this issue. 3. The satyr package from EPEL is newer than the version included in CentOS-6.7. The package from EPEL seems to work OK as well, but they are likely to remove it as it also conflicts with RHEL-6.7. We have not observed any negative impacts from this issue. 4. yum-plugin-downloadonly has been obsoleted by yum, and the functionality is now built into the default yum. More information: 1. These CentOS packages are built from the RHEL-6.7 source code released by Red Hat on July 22, 2015. Please review the release and technical notes for that release here: http://red.ht/1JnEsVQ http://red.ht/1gdBkRu 2. The CentOS release notes for CentOS-6.7, currently a work in progress and not really complete until the final 6.7 release, are available here: http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.7 3. The package set includes 244 Source RPMs updated and are broken down as: 22 Security Updates: 0 Critical Security 2 Important Security 16 Moderate Security 4 Low Security 25 Enhancement Updates 197 Bugfix Updates Individual per-package release announcements are available here: http://lists.centos.org/pipermail/centos-cr-announce/2015-July/thread.html -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net

1 0

wicd problem 0: i have started having problems wicd and network connections
by g 27 Jul '15

27 Jul '15

greetings, system: CentOS = 6.6 - current updates KDE = 4.3.4 Network Manager = 0.8.1 wicd = 1.7.0 (bzr-r552) from what i have read in threads, it appears that 'wicd' is recommended network controller over 'network manager'. because of this, i installed wicd and tried to use. i find this strange because i see problems when using 'wicd'. in attempt to understand what and where problem may be, i have tried various ways of checking for problem. to post what i have found, i am posting in 6 parts to hopefully make it easier for help in troubleshooting by breaking down what i have found. comments and suggestions most welcome. tia. -- If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.6 tc,hago. g .

3 2

wicd problem 5: wicd restarts itself when as user making terminal commands
by g 27 Jul '15

27 Jul '15

greetings, following are command line problems as user using virtual terminals. ]$ ifconfig;date eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1419 errors:0 dropped:0 overruns:0 frame:0 TX packets:709 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:117028 (114.2 KiB) TX bytes:87298 (85.2 KiB) Interrupt:19 Memory:f0180000-f01a0000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:334 errors:0 dropped:0 overruns:0 frame:0 TX packets:334 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25264 (24.6 KiB) TX bytes:25264 (24.6 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3505 (3.4 KiB) Sun Jul 26 21:43:27 CDT 2015 [geo@boxen ~]$ sudo ifconfig eth0 down;date [sudo] password for geo: Sun Jul 26 21:44:26 CDT 2015 [geo@boxen ~]$ ifconfig;date eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1454 errors:0 dropped:0 overruns:0 frame:0 TX packets:722 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:119920 (117.1 KiB) TX bytes:88850 (86.7 KiB) Interrupt:19 Memory:f0180000-f01a0000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:334 errors:0 dropped:0 overruns:0 frame:0 TX packets:334 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25264 (24.6 KiB) TX bytes:25264 (24.6 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3505 (3.4 KiB) Sun Jul 26 21:44:39 CDT 2015 [geo@boxen ~]$ sudo ifconfig eth0 down;date Sun Jul 26 21:45:08 CDT 2015 [geo@boxen ~]$ ifconfig;date eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:1471 errors:0 dropped:0 overruns:0 frame:0 TX packets:746 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:121128 (118.2 KiB) TX bytes:93189 (91.0 KiB) Interrupt:19 Memory:f0180000-f01a0000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:334 errors:0 dropped:0 overruns:0 frame:0 TX packets:334 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25264 (24.6 KiB) TX bytes:25264 (24.6 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3505 (3.4 KiB) Sun Jul 26 21:45:13 CDT 2015 [geo@boxen ~]$ ifconfig;date eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1483 errors:0 dropped:0 overruns:0 frame:0 TX packets:778 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:122580 (119.7 KiB) TX bytes:99082 (96.7 KiB) Interrupt:19 Memory:f0180000-f01a0000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:334 errors:0 dropped:0 overruns:0 frame:0 TX packets:334 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25264 (24.6 KiB) TX bytes:25264 (24.6 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3505 (3.4 KiB) Sun Jul 26 21:45:48 CDT 2015 [geo@boxen ~]$ sudo ifconfig eth0 down;date Sun Jul 26 21:45:58 CDT 2015 [geo@boxen ~]$ ifconfig;date lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:334 errors:0 dropped:0 overruns:0 frame:0 TX packets:334 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25264 (24.6 KiB) TX bytes:25264 (24.6 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3505 (3.4 KiB) Sun Jul 26 21:46:02 CDT 2015 [geo@boxen ~]$ ifconfig;date lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:334 errors:0 dropped:0 overruns:0 frame:0 TX packets:334 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25264 (24.6 KiB) TX bytes:25264 (24.6 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3505 (3.4 KiB) Sun Jul 26 21:46:19 CDT 2015 [geo@boxen ~]$ ifconfig;date lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:334 errors:0 dropped:0 overruns:0 frame:0 TX packets:334 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25264 (24.6 KiB) TX bytes:25264 (24.6 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3505 (3.4 KiB) Sun Jul 26 21:46:43 CDT 2015 [geo@boxen ~]$ ifconfig;date lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:334 errors:0 dropped:0 overruns:0 frame:0 TX packets:334 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25264 (24.6 KiB) TX bytes:25264 (24.6 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3505 (3.4 KiB) Sun Jul 26 21:48:28 CDT 2015 [geo@boxen ~]$ ifconfig;date eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1565 errors:0 dropped:0 overruns:0 frame:0 TX packets:829 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:128932 (125.9 KiB) TX bytes:106267 (103.7 KiB) Interrupt:19 Memory:f0180000-f01a0000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:334 errors:0 dropped:0 overruns:0 frame:0 TX packets:334 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25264 (24.6 KiB) TX bytes:25264 (24.6 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:23 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3505 (3.4 KiB) Sun Jul 26 21:50:38 CDT 2015 [geo@boxen ~]$ as can be seen from above, wicd is again restarting network connection, tho restart did take longer for some unknown reason. -- If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.6 tc,hago. g .

1 0

wicd problem 4: wicd restarts itself when as root user making terminal commands
by g 27 Jul '15

27 Jul '15

greetings, to further check wicd problem, i decided to run test as root user and as user. i verified wicd problems 1, 2, 3 happen when logged in as root user. to further test wicd problems, i tried a few command line problems using virtual terminals. in following, note changing of status for eth0. [root@boxen Documents]# ifconfig eth0 down [root@boxen Documents]# ifconfig eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:886 errors:0 dropped:0 overruns:0 frame:0 TX packets:491 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:78924 (77.0 KiB) TX bytes:63994 (62.4 KiB) Interrupt:19 Memory:f0180000-f01a0000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:296 errors:0 dropped:0 overruns:0 frame:0 TX packets:296 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22964 (22.4 KiB) TX bytes:22964 (22.4 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3417 (3.3 KiB) [root@boxen Documents]# ifconfig eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:900 errors:0 dropped:0 overruns:0 frame:0 TX packets:520 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:80504 (78.6 KiB) TX bytes:69267 (67.6 KiB) Interrupt:19 Memory:f0180000-f01a0000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:296 errors:0 dropped:0 overruns:0 frame:0 TX packets:296 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22964 (22.4 KiB) TX bytes:22964 (22.4 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3417 (3.3 KiB) [root@boxen Documents]# ifconfig eth0 down;ifconfig;date lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:296 errors:0 dropped:0 overruns:0 frame:0 TX packets:296 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22964 (22.4 KiB) TX bytes:22964 (22.4 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3417 (3.3 KiB) Sun Jul 26 21:30:00 CDT 2015 [root@boxen Documents]# ifconfig;date eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:993 errors:0 dropped:0 overruns:0 frame:0 TX packets:575 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:87572 (85.5 KiB) TX bytes:76022 (74.2 KiB) Interrupt:19 Memory:f0180000-f01a0000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:296 errors:0 dropped:0 overruns:0 frame:0 TX packets:296 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22964 (22.4 KiB) TX bytes:22964 (22.4 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3417 (3.3 KiB) Sun Jul 26 21:30:20 CDT 2015 i used date command to show time interval of eth0 state changing. a 5th problem i see with 'wicd' is in post "Subject: wicd problem"; 5: wicd restarts itself when as user making terminal commands -- If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.6 tc,hago. g .

1 0

wicd problem 3: wicd blocking 1st attempt connection for firefox and yumex
by g 27 Jul '15

27 Jul '15

greetings, wicd is preventing firefox and yumex to connect to internet. when i first try to connect to a web site with firefox, i get err message; Unable to connect when i click [Try Again], connection is made. all further connection attempts are ok. when i try to run yumex, i get error message; Not connected to a network. Do you want to continue selecting [Yes] continues starting yumex, but i have active repositories. when i run yum cl command; ]$ yum check-update Loaded plugins: aliases, changelog, downloadonly, fastestmirror, presto, : refresh-packagekit, security, tmprepo, verify, versionlock Determining fastest mirrors Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=6& arch=x86_64&repo=os error was 14: PYCURL ERROR 6 - "Couldn't resolve host 'mirrorlist.centos.org'" Error: Cannot find a valid baseurl for repo: base when i run yum cl command again; ]$ yum check-update Loaded plugins: aliases, changelog, downloadonly, fastestmirror, presto, : refresh-packagekit, security, tmprepo, verify, versionlock Loading mirror speeds from cached hostfile epel/metalink | 13 kB 00:00 which indicates yum has made connection. a 4th problem i see with 'wicd' is in post "Subject: wicd problem"; 4: wicd restarts itself when as root user making terminal commands -- If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.6 tc,hago. g .

1 0

wicd problem 2: wicd does not sync when ifconfig commands are given from a terminal
by g 27 Jul '15

27 Jul '15

greetings, during past week or so, i have been having problems with mozilla firefox locking up kde desktop and i have to open a terminal to reboot system. to insure that i get kde back to a desired state, i make backups of ~/.kde path when ever i change any settings of kde. after system reboots and desktop manager is displayed, i <ctrl+alt+f1> to terminal, delete current ~/.kde, then copy ~/.kde-backup to ~/.kde. while in terminal, i run 'ifconfig' to see if network is connected, which it is, so i 'sudo ifconfig eth0 down' to disconnect. after starting kde, wicd icon in system tray is showing wicd has connection to network, which it does not. when i click wicd icon and then select 'disconnect', and close wicd window, then reopen wicd and select 'connect', there is no connection. a 3rd problem i see with 'wicd' is in post "Subject: wicd problem"; 3: wicd blocking 1st attempt connection for firefox and yumex -- If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.6 tc,hago. g .

1 0

wicd problem 1: wicd allows network to be connected on reboot
by g 27 Jul '15

27 Jul '15

greetings, i find this strange because i see problems when using 'wicd'. 1st problem is that wicd allows network to be connected on reboot, even when network is disconnected at time of reboot. such does not seem to be good because i leave system up 24/7/365 and if there is a mains failure and ups takes system down, system will come back up with network connected, which i prefer not to have happen. is there a way to set up 'wicd' so that it does not start connected? a 2nd problem i see with 'wicd' is in post "Subject: wicd problem"; 2: wicd does not sync when ifconfig commands are given from a terminal -- If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.6 tc,hago. g .

1 0

Re: [CentOS] rsyslog.conf
by James B. Byrne 25 Jul '15

25 Jul '15

On Thu, July 23, 2015 13:19, m.roth(a)5-cent.us wrote: > Physically dragging the thread back on topic... > > I really am going crazy, trying to deal with the hourly logs from the > loghost. We've got 170+ servers and workstations... but a *very* large > percentage of what's showing up is from his bloody new fedora 22, with > its idiot systemd logging of *ever* selinux message to > /var/log/messages. > > I tried creating a rule, /etc/rsyslog.d/audit.conf, that reads: > > if $msg contains "audit" and $msg,contains,'res=success' then - > > but that seemed to send *everything* to /dev/null. That was my best > guess, > based on googling (yahooing?) and man pages. Can anyone tell me what's > wrong with that syntax? > > mark > > > And Lennart blames Linus[1] for why he gets hate mail. We are giving RHEL-7 a pass on this iteration. We have installed it on a couple of test hosts and are not favourably impressed with much of the user interface. At least not from the sys-admin side of things. This is not to imply that there is nothing good in 7. There are at lot of improvements that we certainly value. But it is too early in systemd development for us to waste time debugging somebody else's pipe-dream on our dime. We will see what 8 offers and decide then whether to move to something else. [1]. https://plus.google.com/app/basic/stream/z13rdjryqyn1xlt3522sxpugoz3gujbhh04 -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

5 6

Timeout before trust answer with iPhone iOS 8
by David McGuffey 25 Jul '15

25 Jul '15

Until recently I've not had any problem connecting my iPhone 4s with iOS 8 to my CentOS 6.6 desktop to move pictures and videos. Problem occurs with my wife's new iPhone 5s. Now, before I can answer the "Trust This Computer" message on the iPhone, I get a DBus error: "org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)" Searching this message reveals a lot of complaints by users on Ubuntu and a bug in a library. But this was back in 2012-2013. Couldn't find anything related to CentOS. Appears to be a timing issue...the timer expires before I can respond to the trust question on the iPhone. Any guidance on how to fix this? Is there a timeout setting somewhere down in udev, fuse, or gvfs? DaveM

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss