Re: Weird network problem
On 05/25/2013 08:00 PM, Phil Dobbin wrote: Hi, all. I've got several machines on a LAN behind a NAT with DHCP assigning always the same addresses from a dynamic IP. A couple of days ago the IP changed since then, one of the machines running Fedora 17 always fails first time to connect to the network: launch Thunderbird, no start screen, first attempt to check mail, it tells me that there's no network connection, second attempt it connects. The scheduled DejaDup backup always fails with no network but will run manually no problem. Firefox can't find Google but the Nagios web interface is fine as is all the cli stuff (ping, ssh, etc). Most annoyingly, yum update goes through every mirror before partially downloading part of the updates if the updates are large, it takes about three attempts to get them all installed. I'd like to clear this up naturally especially as in the next couple of weeks I'll be upgrading this box to Fedora 18 the last thing I need is a dodgy network connection. All the machines below are on the same LAN they all work fine after the IP address change, it's only the Fedora box that's causing problems. Any help appreciated. I'm stuck. Cheers, Phil... Check your name server settings. Does /etc/resolv.conf have a name server that from the old IP address? Do you have one machine on the network that runs a catching name server and the rest of the Fedora machines are looking for it at the old address? Or are you running something like dnsmasq on the machines, and have the old IP address in the config file? Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Weird network problem
On 05/26/2013 02:21 AM, Joe Zeff wrote: On 05/25/2013 06:00 PM, Phil Dobbin wrote: I've got several machines on a LAN behind a NAT with DHCP assigning always the same addresses from a dynamic IP. A couple of days ago the IP changed since then, one of the machines running Fedora 17 always fails first time to connect to the network: launch Thunderbird, no start screen, first attempt to check mail, it tells me that there's no network connection, second attempt it connects. As long as it always gets the same IP address, why don't you just set it manually? The same address assigned is in the 192.168.1.xxx range is, obviously, internal. The dynamic IP is external this is the one that changes I have no control over it ( I can't get a static IP unfortunately). Cheers, Phil... -- currently (ab)using CentOS 5.9 6.4, Debian Squeeze Wheezy, Fedora Beefy, Spherical That Damn Cat, Lubuntu 12.10, OS X Snow Leopard Ubuntu Precise, Quantal Raring GnuPG Key : http://www.horse-latitudes.co.uk/publickey.asc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Weird network problem
On 05/26/2013 11:54 AM, Mikkel L. Ellertson wrote: On 05/25/2013 08:00 PM, Phil Dobbin wrote: Hi, all. I've got several machines on a LAN behind a NAT with DHCP assigning always the same addresses from a dynamic IP. A couple of days ago the IP changed since then, one of the machines running Fedora 17 always fails first time to connect to the network: launch Thunderbird, no start screen, first attempt to check mail, it tells me that there's no network connection, second attempt it connects. The scheduled DejaDup backup always fails with no network but will run manually no problem. Firefox can't find Google but the Nagios web interface is fine as is all the cli stuff (ping, ssh, etc). Most annoyingly, yum update goes through every mirror before partially downloading part of the updates if the updates are large, it takes about three attempts to get them all installed. I'd like to clear this up naturally especially as in the next couple of weeks I'll be upgrading this box to Fedora 18 the last thing I need is a dodgy network connection. All the machines below are on the same LAN they all work fine after the IP address change, it's only the Fedora box that's causing problems. Any help appreciated. I'm stuck. Cheers, Phil... Check your name server settings. Does /etc/resolv.conf have a name server that from the old IP address? Do you have one machine on the network that runs a catching name server and the rest of the Fedora machines are looking for it at the old address? Or are you running something like dnsmasq on the machines, and have the old IP address in the config file? I've never used any name server settings on any of these machines. The lease is automatically assigned by DHCP so therefore there is no need to. The external link comes into a NAT router then onto a HP ProCurve switch then via cat5 cables to each machine (there's no wireless involved anywhere). Then each machine in Network Settings uses the automatic setting to assign each address DNS (192.168.1.254) address mask (255.255.255.0). As I've said, all other machines (all 16 of them) are fine. It's just the Fedora box which leads me to suspect that Fedora's doing, or not doing something, to cause this. Cheers, Phil... -- currently (ab)using CentOS 5.9 6.4, Debian Squeeze Wheezy, Fedora Beefy, Spherical That Damn Cat, Lubuntu 12.10, OS X Snow Leopard Ubuntu Precise, Quantal Raring GnuPG Key : http://www.horse-latitudes.co.uk/publickey.asc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Weird network problem
On 05/26/2013 07:18 AM, Phil Dobbin wrote: On 05/26/2013 11:54 AM, Mikkel L. Ellertson wrote: On 05/25/2013 08:00 PM, Phil Dobbin wrote: Hi, all. I've got several machines on a LAN behind a NAT with DHCP assigning always the same addresses from a dynamic IP. A couple of days ago the IP changed since then, one of the machines running Fedora 17 always fails first time to connect to the network: launch Thunderbird, no start screen, first attempt to check mail, it tells me that there's no network connection, second attempt it connects. The scheduled DejaDup backup always fails with no network but will run manually no problem. Firefox can't find Google but the Nagios web interface is fine as is all the cli stuff (ping, ssh, etc). Most annoyingly, yum update goes through every mirror before partially downloading part of the updates if the updates are large, it takes about three attempts to get them all installed. I'd like to clear this up naturally especially as in the next couple of weeks I'll be upgrading this box to Fedora 18 the last thing I need is a dodgy network connection. All the machines below are on the same LAN they all work fine after the IP address change, it's only the Fedora box that's causing problems. Any help appreciated. I'm stuck. Cheers, Phil... Check your name server settings. Does /etc/resolv.conf have a name server that from the old IP address? Do you have one machine on the network that runs a catching name server and the rest of the Fedora machines are looking for it at the old address? Or are you running something like dnsmasq on the machines, and have the old IP address in the config file? I've never used any name server settings on any of these machines. The lease is automatically assigned by DHCP so therefore there is no need to. The external link comes into a NAT router then onto a HP ProCurve switch then via cat5 cables to each machine (there's no wireless involved anywhere). Then each machine in Network Settings uses the automatic setting to assign each address DNS (192.168.1.254) address mask (255.255.255.0). As I've said, all other machines (all 16 of them) are fine. It's just the Fedora box which leads me to suspect that Fedora's doing, or not doing something, to cause this. Cheers, Phil... Dumb question - have you checked the network connection? See if changing the cable or the port on the switch helps. It seams strange that the external IP address changing would cause this, but for some strange reason hardware problems totally unrelated to the change seam to pick that time to happen. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Weird network problem
On 05/26/2013 02:54 PM, Mikkel L. Ellertson wrote: On 05/26/2013 07:18 AM, Phil Dobbin wrote: On 05/26/2013 11:54 AM, Mikkel L. Ellertson wrote: On 05/25/2013 08:00 PM, Phil Dobbin wrote: Hi, all. I've got several machines on a LAN behind a NAT with DHCP assigning always the same addresses from a dynamic IP. A couple of days ago the IP changed since then, one of the machines running Fedora 17 always fails first time to connect to the network: launch Thunderbird, no start screen, first attempt to check mail, it tells me that there's no network connection, second attempt it connects. The scheduled DejaDup backup always fails with no network but will run manually no problem. Firefox can't find Google but the Nagios web interface is fine as is all the cli stuff (ping, ssh, etc). Most annoyingly, yum update goes through every mirror before partially downloading part of the updates if the updates are large, it takes about three attempts to get them all installed. I'd like to clear this up naturally especially as in the next couple of weeks I'll be upgrading this box to Fedora 18 the last thing I need is a dodgy network connection. All the machines below are on the same LAN they all work fine after the IP address change, it's only the Fedora box that's causing problems. Any help appreciated. I'm stuck. Cheers, Phil... Check your name server settings. Does /etc/resolv.conf have a name server that from the old IP address? Do you have one machine on the network that runs a catching name server and the rest of the Fedora machines are looking for it at the old address? Or are you running something like dnsmasq on the machines, and have the old IP address in the config file? I've never used any name server settings on any of these machines. The lease is automatically assigned by DHCP so therefore there is no need to. The external link comes into a NAT router then onto a HP ProCurve switch then via cat5 cables to each machine (there's no wireless involved anywhere). Then each machine in Network Settings uses the automatic setting to assign each address DNS (192.168.1.254) address mask (255.255.255.0). As I've said, all other machines (all 16 of them) are fine. It's just the Fedora box which leads me to suspect that Fedora's doing, or not doing something, to cause this. Cheers, Phil... Dumb question - have you checked the network connection? See if changing the cable or the port on the switch helps. It seams strange that the external IP address changing would cause this, but for some strange reason hardware problems totally unrelated to the change seam to pick that time to happen. I put a brand new cat 5 into another HP ProCurve that I have racked as a backup still the same: 'Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=updates-released-f17arch=x86_64 error was 14: curl#6 - Could not resolve host: mirrors.fedoraproject.org; Name or service not known' Thunderbird still needs three manual attempts to connect too (as you can see, it does work eventually). I've rebooted, looked in logs. I'm at a loss... Cheers, Phil... -- currently (ab)using CentOS 5.9 6.4, Debian Squeeze Wheezy, Fedora Beefy, Spherical That Damn Cat, Lubuntu 12.10, OS X Snow Leopard Ubuntu Precise, Quantal Raring GnuPG Key : http://www.horse-latitudes.co.uk/publickey.asc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Weird network problem
On 05/26/2013 02:54 PM, Mikkel L. Ellertson wrote: [...] Dumb question - have you checked the network connection? See if changing the cable or the port on the switch helps. It seams strange that the external IP address changing would cause this, but for some strange reason hardware problems totally unrelated to the change seam to pick that time to happen. One thing I have noticed in /var/log/messages is it's full of these: 'kernel: [53379.147068] power_supply hid-00:1e:52:f9:5d:dc-battery: driver failed to report `capacity' propert y: -5' Hundreds hundreds of lines. More pertinent are probably these lines: 'kernel: [52915.018110] tg3 :03:00.0 p5p1: Link is down 23384 May 26 16:28:57 pathstar NetworkManager[660]: info (p5p1): carrier now OFF (device state 100, deferring action for 4 seconds)' 'NetworkManager[660]: info (p5p1): device state change: activated - unavailable (reason 'carrier-changed') [100 20 40] 23388 May 26 16:29:01 pathstar NetworkManager[660]: info (p5p1): deactivating device (reason 'carrier-changed') [40] 23389 May 26 16:29:01 pathstar NetworkManager[660]: info (p5p1): canceled DHCP transaction, DHCP client pid 852 23390 May 26 16:29:01 pathstar dbus-daemon[685]: dbus[685]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using serviceh elper) 23391 May 26 16:29:01 pathstar dbus[685]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) 23392 May 26 16:29:01 pathstar dbus-daemon[685]: dbus[685]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 23393 May 26 16:29:01 pathstar dbus[685]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 23394 May 26 16:29:01 pathstar avahi-daemon[662]: Withdrawing address record for 192.168.1.79 on p5p1. 23395 May 26 16:29:01 pathstar avahi-daemon[662]: Leaving mDNS multicast group on interface p5p1.IPv4 with address 192.168.1.79. 23396 May 26 16:29:01 pathstar avahi-daemon[662]: Interface p5p1.IPv4 no longer relevant for mDNS.' These came out at about roughly the same time as Thunderbird was complaining about 'no netowrk connection' Cheers, Phil... -- currently (ab)using CentOS 5.9 6.4, Debian Squeeze Wheezy, Fedora Beefy, Spherical That Damn Cat, Lubuntu 12.10, OS X Snow Leopard Ubuntu Precise, Quantal Raring GnuPG Key : http://www.horse-latitudes.co.uk/publickey.asc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Weird network problem
On Sun, 2013-05-26 at 02:00 +0100, Phil Dobbin wrote: I've got several machines on a LAN behind a NAT with DHCP assigning always the same addresses from a dynamic IP. A couple of days ago the IP changed since then, one of the machines running Fedora 17 always fails first time to connect to the network: All the machines below are on the same LAN they all work fine after the IP address change, it's only the Fedora box that's causing problems. What was the cause for the IP change? Equipment reconfiguration or replacement? The fault may be there... The first thing that springs to mind with some things working and others not, is perhaps MTU is different between the machines, with Fedora's not being a good choice for the network. -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: f17 no internet after power failure, power restored
If it keeps resetting to the same wrong date, chances are the power failure caused your machine's hardware clock to be set to the wrong time. Try first getting your OS system clock set properly (as you have done already), and then use hwclock to sync the hardware clock to the system clock. I have occasionally had to do this in the past. --Greg -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Dual screen video display problem
On 5/26/2013 7:06 PM, David wrote: On 5/26/2013 5:54 PM, Robin Laing wrote: On 2013-05-25 10:25, ergodic wrote: I have a similar problem. In previous Fedoras it was possible to select the monitor to be used during booting or display the booting screen in both monitors. It looks that the distro is becoming less flexible or much harder to configure. It is nice to see that I am not the only one that is having this issue. I wonder where the experts are that can support us or tell us where to submit the bug under. I will give it a few more days and then submit some bug report under some module but not sure yet. i'M NOT AN EXPERT BUT i WOULD START HERE. Red Hat Bugzilla – Main Page https://bugzilla.redhat.com/index.cgi I apologize for the caps. Grandson is visiting this weekend. Fast little rascal. :-) -- David -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Dual screen video display problem
On 5/26/2013 5:54 PM, Robin Laing wrote: On 2013-05-25 10:25, ergodic wrote: I have a similar problem. In previous Fedoras it was possible to select the monitor to be used during booting or display the booting screen in both monitors. It looks that the distro is becoming less flexible or much harder to configure. It is nice to see that I am not the only one that is having this issue. I wonder where the experts are that can support us or tell us where to submit the bug under. I will give it a few more days and then submit some bug report under some module but not sure yet. i'M NOT AN EXPERT BUT i WOULD START HERE. Red Hat Bugzilla – Main Page https://bugzilla.redhat.com/index.cgi -- David -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Dual screen video display problem
On 2013-05-26 17:08, David wrote: On 5/26/2013 7:06 PM, David wrote: On 5/26/2013 5:54 PM, Robin Laing wrote: On 2013-05-25 10:25, ergodic wrote: I have a similar problem. In previous Fedoras it was possible to select the monitor to be used during booting or display the booting screen in both monitors. It looks that the distro is becoming less flexible or much harder to configure. It is nice to see that I am not the only one that is having this issue. I wonder where the experts are that can support us or tell us where to submit the bug under. I will give it a few more days and then submit some bug report under some module but not sure yet. i'M NOT AN EXPERT BUT i WOULD START HERE. Red Hat Bugzilla – Main Page https://bugzilla.redhat.com/index.cgi I apologize for the caps. Grandson is visiting this weekend. Fast little rascal. :-) I do that without a grandson. I forget to proof read as well. :) I have searched bugzilla over and over before coming to the list. Also searched google. Still not finding the same issue. Seeing lots of issues with dual screen but I am not sure which module to look under. During today's searches, I realized that I have not done a full look through the boot sequence to see when the screen changes from single to mirrored(cloned) from single screen. I will check dmesg closer tomorrow at work. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Dual screen video display problem
On 05/26/2013 04:20 PM, Robin Laing wrote: During today's searches, I realized that I have not done a full look through the boot sequence to see when the screen changes from single to mirrored(cloned) from single screen. I will check dmesg closer tomorrow at work. Grep is your friend, here, although you do need to know whether to look for mirrored or for clone. You may want to give the same treatment to /var/log/boot.log while you're at it. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Error installing a package ??
Fedora 18, Trying to install a package, nitroshare-0.2-2.i386.rpm and I get the following error message, What Gives ?? # yum -y localinstall nitroshare-0.2-2.i386.rpm Loaded plugins: keys, langpacks, presto, refresh-packagekit, versionlock Examining nitroshare-0.2-2.i386.rpm: nitroshare-0.2-2.i386 Marking nitroshare-0.2-2.i386.rpm to be installed Resolving Dependencies -- Running transaction check --- Package nitroshare.i386 0:0.2-2 will be installed -- Finished Dependency Resolution Dependencies Resolved === Package Arch Version Repository Size === Installing: nitroshare i386 0.2-2 /nitroshare-0.2-2.i386 642 k Transaction Summary === Install 1 Package Total size: 642 k Installed size: 642 k Downloading Packages: Running Transaction Check Running Transaction Test Transaction Check Error: file / from install of nitroshare-0.2-2.i386 conflicts with file from package filesystem-3.1-2.fc18.i686 Error Summary - -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: f17 no internet after power failure, power restored
If it keeps resetting to the same wrong date, chances are the power failure caused your machine's hardware clock to be set to the wrong time. Try first getting your OS system clock set properly (as you have done already), and then use hwclock to sync the hardware clock to the system clock. I have occasionally had to do this in the past. --Greg # hwclock Thu 26 May 2011 03:13:54 PM PDT -0.371612 secondssame old 2011 date # hwclock --show Thu 26 May 2011 03:28:27 PM PDT -0.747409 secondssame old 2011 date [root@F17sda10 ~]# hwclock --systohc [root@F17sda10 ~]# [root@F17sda10 ~]# hwclock Sun 26 May 2013 04:09:41 PM PDT -0.755945 seconds looks like it took! I am concerned re notes section from 'man hwclock' It is important that the System Time not have any dis‐ continuities such as would happen if you used the date(1L) program to set it while the system is running. which I did,as per earlier Do you expect trouble from this? thanks Jack -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Error installing a package ??
On 05/27/13 08:19, Jim wrote: Fedora 18, Trying to install a package, nitroshare-0.2-2.i386.rpm and I get the following error message, What Gives ?? You have downloaded a poorly packaged application. It is potentially making changes to permissions and/or selinux contexts on /, /usr, /opt and other directories. I would report this issue to the folks supplying the package. You could force install it...which may break things. # yum -y localinstall nitroshare-0.2-2.i386.rpm Loaded plugins: keys, langpacks, presto, refresh-packagekit, versionlock Examining nitroshare-0.2-2.i386.rpm: nitroshare-0.2-2.i386 Marking nitroshare-0.2-2.i386.rpm to be installed Resolving Dependencies -- Running transaction check --- Package nitroshare.i386 0:0.2-2 will be installed -- Finished Dependency Resolution Dependencies Resolved === Package Arch Version Repository Size === Installing: nitroshare i386 0.2-2 /nitroshare-0.2-2.i386 642 k Transaction Summary === Install 1 Package Total size: 642 k Installed size: 642 k Downloading Packages: Running Transaction Check Running Transaction Test Transaction Check Error: file / from install of nitroshare-0.2-2.i386 conflicts with file from package filesystem-3.1-2.fc18.i686 Error Summary - -- The only thing worse than a poorly asked question is a cryptic answer. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re[2]: Error installing a package ??
On 05/26/2013 at 07:38 PM, Ed Greshko ed.gres...@greshko.com wrote: On 05/27/13 08:19, Jim wrote: Fedora 18, Trying to install a package, nitroshare-0.2-2.i386.rpm and I get the following error message, What Gives ?? You have downloaded a poorly packaged application. It is potentially making changes to permissions and/or selinux contexts on /, /usr, /opt and other directories. I would report this issue to the folks supplying the package. You could force install it...which may break things. With such files I have on occasion used... # cp rpmfile.rpm /tmp # cd /tmp # rpm2cpio rpmfile.rpm | cpio -idmv ...and then copied the resulting file structure to where it needs to go. But usually I do that only in a pinch when I really need a package and can find it in no other format than the improperly packaged rpm file. -- Len Philpot l...@philpot.org http://lphilpot.zenfolio.com http://www.mostimportantthing.org -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: f17 no internet after power failure, power restored
On Sun, 2013-05-26 at 17:36 -0700, jackson byers wrote: I am concerned re notes section from 'man hwclock' It is important that the System Time not have any dis‐ continuities such as would happen if you used the date(1L) program to set it while the system is running. which I did,as per earlier Do you expect trouble from this? Not really. It can do weird things with cron job scheduling and the like, but I think they're just warning you not to do this kind of thing willy-nilly. But in your case, it sounds like a one-off due to the power hit. If you find that this happens again, then you may have a bad hardware clock, failing CMOS battery, or some other hardware issue. --Greg -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
