On 06/09/2017 07:29 PM, Ed Greshko wrote:
On 06/10/17 10:22, Ed Greshko wrote:
FWIW, so far I've seen no ill effects from updating to
libdb-5.3.28-21.fc25. However, I should note that I had previously
updated to libdb-5.3.28-16 from testing also with no ill effects.
Oh, I just realized I upda
Ed Greshko wrote:
> On 06/10/17 07:55, Timothy Ward wrote:
>> Do you have to upgrade Alpha to Beta and then to general
release
>> version software as it becomes available or is it upgraded
to the
>> latest available version as Beta or general release becomes
available.
>
>
> No, you don't hav
I think you're probably right on both counts. I thought so before my Thursday
night post, but really thought it best to check with the experts.
thanks,
Bill.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-
It's believed that the main problems were i-node problems identified by "fsck"
during boot. The first time, they were on sda6; the second time, they were on
sda7.
A few follow-up questions about the hard drive... I used the long but
non-destructive test options of both "badblocks" and "smartc
On Fri, 9 Jun 2017 18:20:39 -0700
Samuel Sieb wrote:
> On 06/09/2017 06:12 PM, stan wrote:
> > rm /var/lib/rpm/__db.00? # optional?
> That's not deleting the RPM database, just removing temporary files
> that rpm uses.
Thanks for the clarification.
On Sat, 10 Jun 2017 10:22:17 +0800
Ed Greshko wrote:
> FWIW, so far I've seen no ill effects from updating to
> libdb-5.3.28-21.fc25. However, I should note that I had previously
> updated to libdb-5.3.28-16 from testing also with no ill effects.
I suppose the subject should be *might* break t
On 06/10/17 10:22, Ed Greshko wrote:
> On 06/10/17 09:12, stan wrote:
>> There is an update (or test update) of libdb for F25 that, when
>> installed, breaks the rpm database because it is incompatible. The dnf
>> update completes, and then hangs (at least it did on my system). The
>> fix is to r
On 06/10/17 09:12, stan wrote:
> There is an update (or test update) of libdb for F25 that, when
> installed, breaks the rpm database because it is incompatible. The dnf
> update completes, and then hangs (at least it did on my system). The
> fix is to remove the old rpm databases (this might be
On 06/09/2017 06:12 PM, stan wrote:
There is an update (or test update) of libdb for F25 that, when
installed, breaks the rpm database because it is incompatible. The dnf
update completes, and then hangs (at least it did on my system). The
fix is to remove the old rpm databases (this might be o
There is an update (or test update) of libdb for F25 that, when
installed, breaks the rpm database because it is incompatible. The dnf
update completes, and then hangs (at least it did on my system). The
fix is to remove the old rpm databases (this might be optional), and
rebuild the rpm database
On 06/09/2017 12:09 AM, Jeandet Alexis wrote:
On startup postgreslq always fail to start complaining about port 5432.
My first guess would be that you've configured postgresql to listen on a
specific IP address, and when you do that, the service needs to depend
on "network-online.target" ins
On 06/10/17 07:55, Timothy Ward wrote:
> Do you have to upgrade Alpha to Beta and then to general release
> version software as it becomes available or is it upgraded to the
> latest available version as Beta or general release becomes available.
No, you don't have to do that. As a matter of fac
Do you have to upgrade Alpha to Beta and then to general release
version software as it becomes available or is it upgraded to the
latest available version as Beta or general release becomes available.
___
users mailing list -- users@lists.fedoraproject.o
On 06/09/2017 12:09 AM, Jeandet Alexis wrote:
I have a server running F25 with postgresql and firewald configured.
On startup postgreslq always fail to start complaining about port 5432.
I did allow this port on the firewall, if I start manually postgresql
after it works.
Can you paste the ex
Gordon Messmer wrote:
>> In any case, if that solution isn't workable for you, you can remove
>> "mdns4_minimal [NOTFOUND=return]" from /etc/nsswitch.conf, and you
>> should be able to look up .local hosts using DNS.
Tom Horsley:
> On every system I've ever tried *all* dns lookups always
> fail
Allegedly, on or about 09 June 2017, William Mattison sent:
> * Hard drive? Somewhat unlikely. Two 4-hour non-destructive disk
> checks found no issues. System cleaned; cables dis- and re-connected;
> hard drive removed and put back in; no kinky cables seen. Destructive
> testing and replacing
Allegedly, on or about 09 June 2017, Ed Greshko sent:
> Probably, eventually. After I study the differences between the
> headers of an S/MIME message to the list compared with the headers of
> a PGP/MIME message (which I have verified does survive) and determine
> if it is a case of real breakag
On Fri, 2017-06-09 at 02:51 +, William Mattison wrote:
> I did my weekly patches this afternoon, and this time the system
> booted up fine. So I'm back to what caused the problems.
> * Motherboard battery? Quite unlikely, but not 100%
> certain. Battery replaced anyway.
> * Hard drive? Some
Hi,
On Wed, Jun 7, 2017 at 10:11 AM, Rick Stevens wrote:
> I haven't edited the message so others can take a shot.
>
> We still use MRTG as a part of Nagios and Cacti in our monitoring
> systems but I haven't done any manual configs in a very long time. One
> common thing to keep in mind is that
Hello,
I have a server running F25 with postgresql and firewald configured.
On startup postgreslq always fail to start complaining about port 5432.
I did allow this port on the firewall, if I start manually postgresql
after it works.
So I did plot the startup sequence (systemd-analyse plot), I saw
20 matches
Mail list logo
