[CentOS] Need help with Linux networking interfaces and NIC bonding
Hello everyone I am running into some strange issues when configuring networking interfaces on my physical server running Centos 7.5. Let me give you an overview of what's going on: We have a physical server, running CentOS 7.5. This server has one 4 port NIC and one 2 port NIC and a Dell IDRAC port. The first port of the 4 port NIC, em1, is used for Management traffic. The first port of the 2 port NIC, is used for the second port in the NIC bond, device p6p2. The second port on the 4 port NIC, device em2 is the first, port on the NIC bond. These interfaces are using Static IPs. Here is my /etc/sysconfig/network-scripts/ifcfg-em1 file. Please keep in mind that I have changed the IPs and MAC addresses in the files for security reasons: ifcfg-em1: TYPE="Ethernet" PROXY_METHOD="none" BROWSER_ONLY="no" BOOTPROTO="none" DEFROUTE="yes" IPV4_FAILURE_FATAL="no" IPV6INIT="yes" IPV6_AUTOCONF="yes" IPV6_DEFROUTE="yes" IPV6_FAILURE_FATAL="no" IPV6_ADDR_GEN_MODE="stable-privacy" NAME="em1" UUID="bbb2f9c2-141b-4a99-ab1e-328551aae612" DEVICE="em1" ONBOOT="yes" IPADDR="192.168.56.50" PREFIX="24" GATEWAY="192.168.56.1" DNS1="192.168.126.10" DNS2="192.168.220.10" IPV6_PRIVACY="no" NM_CONTROLLED=no as for the ifcfg-bond0 (the configuration file for the NIC bond, which is bond0): DEVICE=bond0 NAME=bond0 TYPE=Bond ONBOOT=yes BOOTPROTO=none IPADDR=192.168.56.70 PREFIX=24 BONDING_MASTER=yes BONDING_OPT="mode=1 miimon=100" TYPE=Ethernet and the ifcfg-slave1 configuration file, which is the first slave port for the NIC bond, this corresponds to em2: DEVICE=em2 HWADDR="c8:2f:87:fg:2a:31" ONBOOT=yes TYPE=Ethernet BOOTPROTO=none MASTER=bond0 SLAVE=yes and the ifcfg-slave2 configuration file , which corresponds to the second slave port for the NIC bond, which is interface p6p2: DEVICE=p6p2 HWADDR="00:6a:d7:7c:e8:09" BOOTPROTO=none ONBOOT=yes TYPE=Ethernet MASTER=bond0 SLAVE=yes I created a custom routing policy for the NIC bond, bond0. Here is the configuration for the routing policy: route-bond0: 192.168.56.0/24 dev bond0 src 192.168.56.70 table t1 default via 192.168.56.1 dev bond0 table t1 and the rule-bond0 file: table t1 from 192.168.56.70 as for the routing table: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0192.168.56.10.0.0.0 UG0 00 bond0 192.168.56.00.0.0.0 255.255.255.0 U 0 00 bond0 192.168.56.00.0.0.0 255.255.255.0 U 0 00 em1 169.254.0.0 0.0.0.0 255.255.0.0 U 1002 00 em1 169.254.0.0 0.0.0.0 255.255.0.0 U 1008 00 bond0 now here is the scenario I am dealing with: This linux server is used for monitoring purposes. We have Nagios, Cacti and other tools installed on it. There are a few things I have noticed and I want help on: 1) Whenever I ping any of the devices on our network, from this server, the traffic goes out from the management port. I do not want the traffic to go out of the management port. I want it to go out through the active port of the NIC bond. How do I configure the networking so that all primary network traffic flows to and from the NIC bonded interfaces? I only want the management port to be used for SSH purposes and well, management of the server. 2) I have configured the NIC bond in active-backup mode. I notice that when I used another computer to do a continuous ping to the NIC bond, and then I disable one of the slave interfaces of the bond, the ping drops and it does not failover to the backup slave interface and turn into the active one. It also causes any pings to the management port to drop as well. Then when I disable slave2, and enable slave1, the traffic does not fail over to slave1 and the ping continuously fails. It is only when I enable both slave interfaces and then either restart the networking using systemctl restart network, or reboot the server, the networking resumes and the pings succeed again. What steps should I take to fix this issue? Should I even use active-backup mode with the NIC bond or is there a better mode I should use? 3) Ive tested the networking, by changing the VLAN of the NIC bonded ports, on the switch, to a different VLAN, and it caused the management port to stop responding to ping. Why is this and how do I fix that if I decide to one day use two different VLANs for Management and the NIC bond ports? Thank you for all of your help in advance! Sean ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Trouble installing with Nvidia card
> Am 03.10.2018 um 22:29 schrieb Elliott Balsley : > >> >> Why? 7.5.1804 has been out since May of this year. You're going to >> end up downloading a ton of updates the first time. >> > > For a specialized software, we have to wait for the developers to certify > each new OS. They are still recommending 7.3. One reason in particular is > that 7.5 has a fix for Meltdown and Spectre, which known to reduce > performance. This machine will be airgapped, so performance trumps > security. Controlling the Performance Impact https://access.redhat.com/articles/3311301 > >> I suggest going into the BIOS and disable the internal video port, if >> that's possible. You might be able to indicate which video device to >> use for default with the right video= parameter to the kernel for the >> bootloader. >> >> This is not possible. The best I can do is switch VGA priority to > offboard, that controls which screen shows POST messages. > Also — this time it shows a few more lines, nouveau says unknown chipset > (132000a1) > So I think I can fix it by adding nomodeset to the boot options. > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 2038 year Problem
On 10/02/18 13:41, Johann Fock wrote: Hallo Im using CentOS 7 Ist the 2038 year Problem solved in CentOS 7.5 64 bit Version Thanks Johann Fock Hey Johann, You should submit this question to the Fedora mailing list. CentOS is downstream from Fedora. If the problem is not fixed there it will not be fixed in CentOS, no matter what the release number might be in 2038. -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Trouble installing with Nvidia card
> > Why? 7.5.1804 has been out since May of this year. You're going to > end up downloading a ton of updates the first time. > For a specialized software, we have to wait for the developers to certify each new OS. They are still recommending 7.3. One reason in particular is that 7.5 has a fix for Meltdown and Spectre, which known to reduce performance. This machine will be airgapped, so performance trumps security. > I suggest going into the BIOS and disable the internal video port, if > that's possible. You might be able to indicate which video device to > use for default with the right video= parameter to the kernel for the > bootloader. > > This is not possible. The best I can do is switch VGA priority to offboard, that controls which screen shows POST messages. Also — this time it shows a few more lines, nouveau says unknown chipset (132000a1) So I think I can fix it by adding nomodeset to the boot options. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Trouble installing with Nvidia card
On Wed, Oct 03, 2018 at 12:49:31PM -0700, Elliott Balsley wrote: > I'm having trouble doing a fresh install of CentOS 7.3. I'm using > the DVD Why? 7.5.1804 has been out since May of this year. You're going to end up downloading a ton of updates the first time. > installer ISO, burned to a USB flash drive. The system is a Supermicro > 7048 with four Nvidia Titan Xp GPUs, and I have the monitor connected to > the first GPU. In the BIOS, VGA priority is set to Offboard, so I am > seeing POST messages (good). > > The CentOS installer begins and shows a few messages on my monitor, but it > stops after "Reached target Basic System" ok. At this point, if I connect > a second monitor to the motherboard VGA port, then I see the installer > continuing on that screen. Is there some way to install without using a > VGA monitor? I suggest going into the BIOS and disable the internal video port, if that's possible. You might be able to indicate which video device to use for default with the right video= parameter to the kernel for the bootloader. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Trouble installing with Nvidia card
Hi all, I'm having trouble doing a fresh install of CentOS 7.3. I'm using the DVD installer ISO, burned to a USB flash drive. The system is a Supermicro 7048 with four Nvidia Titan Xp GPUs, and I have the monitor connected to the first GPU. In the BIOS, VGA priority is set to Offboard, so I am seeing POST messages (good). The CentOS installer begins and shows a few messages on my monitor, but it stops after "Reached target Basic System" ok. At this point, if I connect a second monitor to the motherboard VGA port, then I see the installer continuing on that screen. Is there some way to install without using a VGA monitor? Thanks in advance. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Frefox update from firefox-60.2.0-1.el7.centos.x86_64 to 60.2.1-1.el7.centos.x86_64 lost master password
On Wed, Oct 3, 2018 at 9:19 AM Stephen John Smoogen wrote: > It would seem that the problem is with upstream-upstream's (aka > Firefox) cleaning up of items that are not supposed to be there after > Firefox 58 > > https://bugzilla.mozilla.org/show_bug.cgi?id=1475775 > > It looks like it is deleting files it thinks should have been > converted to a newer more secure version.. but don't seem to be for > some reason. I am not sure if those files will just removed again > every time you restore them. That link added to the related RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1633932 Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Frefox update from firefox-60.2.0-1.el7.centos.x86_64 to 60.2.1-1.el7.centos.x86_64 lost master password
On Wed, 3 Oct 2018 at 06:08, Nicolas Thierry-Mieg wrote: > > On 10/03/2018 11:34 AM, Rob Kampen wrote: > > Hi list, > > > > Did an update to firefox last night and rebooted over night. > > > > Today I find firefox started without asking for master password - funny > > me thinks. > > > > Try to log in to a web service I use and find that my password does not > > appear. > > > > Check preferences and find that no master password is set and the > > password list / table is empty. > > > > As I do not trust my passwords to the cloud I do not save these to my > > firefox profile . so back to manual entry for all my sites wow > > going to be a slow month as I reset scores of passwords. > > > > Any one else have this problem and any clues as to what causes this? I > > am concerned if this should happen again, as I have saved passwords for > > many scores of web services. > > Hi, > > haven't had that, but restoring logins.json and key3.db in > ~/.mozilla/firefox/.../ from your latest backup should do the trick. > It would seem that the problem is with upstream-upstream's (aka Firefox) cleaning up of items that are not supposed to be there after Firefox 58 https://bugzilla.mozilla.org/show_bug.cgi?id=1475775 It looks like it is deleting files it thinks should have been converted to a newer more secure version.. but don't seem to be for some reason. I am not sure if those files will just removed again every time you restore them. > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos -- Stephen J Smoogen. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CERN Dojo in 2 weeks: Registration closes soon
A reminder: The CERN Dojo will be held in Meyrin, Switzerland, on October 19th, and registration closes soon, as we have to issue security badges for all attendees. Attendance is free, but you must register to get in the front door. We'll have a full day of deep-dive CentOS content, in the midst of one of the most famous research facilities in the world. You don't want to miss it! http://cern.ch/centos See you at CERN! -- Rich Bowen - rbo...@redhat.com @CentOSProject // @rbowen 859 351 9166 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Frefox update from firefox-60.2.0-1.el7.centos.x86_64 to 60.2.1-1.el7.centos.x86_64 lost master password
On Wed, 2018-10-03 at 12:08 +0200, Nicolas Thierry-Mieg wrote: > On 10/03/2018 11:34 AM, Rob Kampen wrote: > > Hi list, > > > > Did an update to firefox last night and rebooted over night. > > > > Today I find firefox started without asking for master password - > > funny > > me thinks. > > > > Try to log in to a web service I use and find that my password does > > not > > appear. > > > > Check preferences and find that no master password is set and the > > password list / table is empty. > > > > As I do not trust my passwords to the cloud I do not save these to > > my > > firefox profile . so back to manual entry for all my sites > > wow > > going to be a slow month as I reset scores of passwords. > > > > Any one else have this problem and any clues as to what causes > > this? I > > am concerned if this should happen again, as I have saved passwords > > for > > many scores of web services. > > Hi, > > haven't had that, but restoring logins.json and key3.db in > ~/.mozilla/firefox/.../ from your latest backup should do the trick. > I had the same problem. Upgraded to the latest firefox last saturday everything looked ok all day. Logged in on monday to find my master password and all my stored passwords were gone. Unfortunately I had done a backup of the home directories later on saturday. So restoring the key3.db and logins.json files didn't work. The problem seems to be with the key3.db file. When the latest firefox (re)creates it, it has the wrong permissions -rw---. 1 molloyt molloyt1137 Oct 3 16:09 logins.json -rw---. 1 molloyt molloyt 16384 Oct 3 14:48 key3.db I removed firefox, deleted the .mozilla directory and reinstalled firefox. But the problem remains. 1. Delete the logins.json and key3.db files 2. Start firefox key3.db file created with the above permissions and selinux context looks ok 3. Set master password and a few account passwords 4. Check they're there in preferences, ok logins.json file created with above permissions 5. login/out a few times to the accounts to make sure everything works,ok 6. Shutdown firefox and restart it, account settings ok and working but key3.db file gone 7. Shutdown firefox and restart it, master password and accounts gone check recreated key3.db file and it has permissions as above. I'm stumped. Any ideas gratefully accepted ;-) Tony. > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos -- Tony Molloy Home ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CERN Dojo in 2 weeks: Registration closes soon
A reminder: The CERN Dojo will be held in Meyrin, Switzerland, on October 19th, and registration closes soon, as we have to issue security badges for all attendees. Attendance is free, but you must register to get in the front door. We'll have a full day of deep-dive CentOS content, in the midst of one of the most famous research facilities in the world. You don't want to miss it! http://cern.ch/centos See you at CERN! -- Rich Bowen - rbo...@redhat.com @CentOSProject // @rbowen 859 351 9166 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 2038 year Problem
On Wed, 3 Oct 2018 at 09:50, Johnny Hughes wrote: > > On 10/02/2018 12:41 PM, Johann Fock wrote: > > Hallo > > Im using CentOS 7 > > Ist the 2038 year Problem solved in CentOS 7.5 64 bit Version > > > > Well, CentOS-7 will be EOL'ed on 30 June 2024 so does it matter? If you have code which is calculating 20 year mortgages and a base CentOS program gives you negative time in 64 bits then it is a problem even if the OS is not going to be around in 2038. [This is where problems were showing up in 1998 and 2008 when 40 year and 30 year contracts/mortgages started getting used in some sort of software and getting weird times.] -- Stephen J Smoogen. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 2038 year Problem
On Wed, Oct 03, 2018 at 10:04:57AM -0400, Robert Heller wrote: > At Wed, 3 Oct 2018 08:49:56 -0500 CentOS mailing list > wrote: > > > > > > > From: Johnny Hughes > > To: centos@centos.org > > Message-ID: > > Subject: Re: [CentOS] 2038 year Problem > > References: <8831b7ae-76c1-4cf1-815c-ef52d4c5d...@abas.de> > > In-Reply-To: <8831b7ae-76c1-4cf1-815c-ef52d4c5d...@abas.de> > > > > On 10/02/2018 12:41 PM, Johann Fock wrote: > > > Hallo > > > Im using CentOS 7 > > > Ist the 2038 year Problem solved in CentOS 7.5 64 bit Version > > > > > > > Well, CentOS-7 will be EOL'ed on 30 June 2024 so does it matter? > > > > It is my understanding that even 32-bit kernels since 2.6 (or maybe even 2.4) > use 64 bit system clocks. The "2038 year Problem" has been solved for some > time... there's solved, then there's solved. anything that uses future dates later than 2038-ageddon will still have trouble, at least until such time as they are all recompiled against kernels and glibc that contain working mitigations. You can't convince me that there aren't a lot of programs and databases/files storing such things. and as time goes by it'll get larger, even before 2038 hits. -- Fred Smith -- fre...@fcshome.stoneham.ma.us - "And he will be called Wonderful Counselor, Mighty God, Everlasting Father, Prince of Peace. Of the increase of his government there will be no end. He will reign on David's throne and over his kingdom, establishing and upholding it with justice and righteousness from that time on and forever." --- Isaiah 9:7 (niv) -- ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 2038 year Problem
At Wed, 3 Oct 2018 08:49:56 -0500 CentOS mailing list wrote: > > > From: Johnny Hughes > To: centos@centos.org > Message-ID: > Subject: Re: [CentOS] 2038 year Problem > References: <8831b7ae-76c1-4cf1-815c-ef52d4c5d...@abas.de> > In-Reply-To: <8831b7ae-76c1-4cf1-815c-ef52d4c5d...@abas.de> > > On 10/02/2018 12:41 PM, Johann Fock wrote: > > Hallo > > Im using CentOS 7 > > Ist the 2038 year Problem solved in CentOS 7.5 64 bit Version > > > > Well, CentOS-7 will be EOL'ed on 30 June 2024 so does it matter? > It is my understanding that even 32-bit kernels since 2.6 (or maybe even 2.4) use 64 bit system clocks. The "2038 year Problem" has been solved for some time... > Content-Description: OpenPGP digital signature > > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.22 (GNU/Linux) > > iEYEARECAAYFAlu0yQQACgkQTKkMgmrBY7OL3QCdFv/zLj3XKrO/ZmSroy385U3w > 6DgAnRdNhwgVbda9ePu5nqlnWmtCLeKx > =Fq4j > -END PGP SIGNATURE- > > MIME-Version: 1.0 > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > > > -- Robert Heller -- 978-544-6933 Deepwoods Software-- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services hel...@deepsoft.com -- Webhosting Services ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 2038 year Problem
On 10/03/2018 08:49 AM, Johnny Hughes wrote: > On 10/02/2018 12:41 PM, Johann Fock wrote: >> Hallo >> Im using CentOS 7 >> Ist the 2038 year Problem solved in CentOS 7.5 64 bit Version >> > > Well, CentOS-7 will be EOL'ed on 30 June 2024 so does it matter? > Putting it another way .. the first ever CentOS release happened in 2004 (CentOS 3.1). That is 14 years ago. 2038 is 14 years AFTER CentOS-7 EOLs. Who asks if anything runs on CentOS 3.1 right now? signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 2038 year Problem
On 10/02/2018 12:41 PM, Johann Fock wrote: > Hallo > Im using CentOS 7 > Ist the 2038 year Problem solved in CentOS 7.5 64 bit Version > Well, CentOS-7 will be EOL'ed on 30 June 2024 so does it matter? signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 2038 year Problem
On Tue, Oct 2, 2018 at 9:46 PM Mark Rousell wrote: > > On 02/10/2018 18:46, Larry Martell wrote: > > I got 2 years of work solving the year 2000 issue. > > I don't think I've ever said this but I am very envious of all these > people who had loads of work due to Y2K or were paid obscene amounts of > money to tend systems over new year's eve/day. > > I was working for an ISP at the time and got none of this. Nothing > happened. I don't even recall any special precautions being taken (apart > from below). No over time, no obscene amounts of money. > > Admittedly there was a Y2K audit earlier in the year and so I presume > that the consultants who did it got paid some obscene amounts of money. > As I recall, they found very little except for one major system that we > knew would need updating anyway. And I presume that the contractor who > came in to fix the major system was rather well paid too. > > But no money for me. Wrong job, wrong time, wrong place, I guess. > Perhaps I should be pleased the actual 99/00 changeover went so smoothly > afterall. It only went smoothly because there were people like me fixing the issues ;-) I worked on Wall St at the time, and I got a reputation for being able to find and fix Y2K issues. Really all that I did was grep the code bases for 2 digit years, and code that blindly added 1900 to them. There were a ton of those cases. It was not atypical for me to find 500-1000 or more such cases at each site. The fixes were easy but the testing took a while. I did this for banks, hedge funds, brokerages, bond traders, etc. At one place where I had fixed probably 700 cases, after Y2K came and went without an incident the CEO said "You made such a big deal about this, and then nothing happened." ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Frefox update from firefox-60.2.0-1.el7.centos.x86_64 to 60.2.1-1.el7.centos.x86_64 lost master password
On 10/03/2018 11:34 AM, Rob Kampen wrote: Hi list, Did an update to firefox last night and rebooted over night. Today I find firefox started without asking for master password - funny me thinks. Try to log in to a web service I use and find that my password does not appear. Check preferences and find that no master password is set and the password list / table is empty. As I do not trust my passwords to the cloud I do not save these to my firefox profile . so back to manual entry for all my sites wow going to be a slow month as I reset scores of passwords. Any one else have this problem and any clues as to what causes this? I am concerned if this should happen again, as I have saved passwords for many scores of web services. Hi, haven't had that, but restoring logins.json and key3.db in ~/.mozilla/firefox/.../ from your latest backup should do the trick. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Frefox update from firefox-60.2.0-1.el7.centos.x86_64 to 60.2.1-1.el7.centos.x86_64 lost master password
Hi list, Did an update to firefox last night and rebooted over night. Today I find firefox started without asking for master password - funny me thinks. Try to log in to a web service I use and find that my password does not appear. Check preferences and find that no master password is set and the password list / table is empty. As I do not trust my passwords to the cloud I do not save these to my firefox profile . so back to manual entry for all my sites wow going to be a slow month as I reset scores of passwords. Any one else have this problem and any clues as to what causes this? I am concerned if this should happen again, as I have saved passwords for many scores of web services. TIA Rob ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos7/Kde4 freeze
Le 18/09/2018 à 10:04, Patrick Begou a écrit : > Hi > > I have a fresh install of centos 7.4 with KDE on a laptop (latitude > 5590) connected to a DELL WD15 dockstation with an additionnal screen. > It works quite well, I have 2 screens side by side (default config), > but > If I add a second menu bar for the screen connected to the dockstation > (KDE allow for this) it is not possible anymore to start a kde session > if the laptop is not connected to the dock station (eg: at home), kde > freeze and never show any menubar. I have to use gnome to login and > remove the .kde directory. > > Is there a way to avoid this ? > > Thanks > > Patrick > This problem seams more general... adding an application to the "favorite" when connected to a docks station produce the same freeze when laptop is standalone. The workaround is to to do this BEFORE connecting to the doc station the first time. :-( I found also some problems with kwallet when seting up a wifi connection: it was requesting for a password but kwallet/centos was unable to focus in the popup windows to allow entering the password...:-\ (standalone laptop at this time) kde seams to have some trouble in dynamic screen configurations. I switched to Xfce which just runs fine and do the job! Patrick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 2038 year Problem
On 03/10/2018 02:46, Mark Rousell wrote: > I don't think I've ever said this but [...] Oops, sorry. This was off-topic here. I actually thought this was a different mail list where it would have been on-topic. -- Mark Rousell ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
