Ned Slider wrote:
Dunc wrote:
Hi
Yes it was written as rpmnew, and indeed the default was the same.
But using the original I was using before, changing nothing, with
[::] I could not connect after the upgrade. I restarted many times,
and eventually changing the original to [*] allowed me
Dunc wrote:
Ned Slider wrote:
Dunc wrote:
Hi
Yes it was written as rpmnew, and indeed the default was the same.
But using the original I was using before, changing nothing, with
[::] I could not connect after the upgrade. I restarted many times,
and eventually changing the original to [*]
Ned Slider wrote:
As this seems to affect the default install configuration we presumably
need to add a note somewhere to reflect this. Thanks for spotting and
reporting it.
Has anyone else experienced this or can confirm it?
There are some of us, who really use IPv6 in real life :D
Karanbir Singh scribbled on Thursday, June 26, 2008 1:31 PM:
Ned Slider wrote:
As this seems to affect the default install configuration we presumably
need to add a note somewhere to reflect this. Thanks for spotting and
reporting it.
Has anyone else experienced this or can confirm it?
[EMAIL PROTECTED] wrote:
Has anyone else experienced this or can confirm it?
There are some of us, who really use IPv6 in real life :D
Somebody's actually using IPv6? One comes to think of flying pigs for some
reason... ;-)
umm. bacon..
- KB
Hi all,
Am I the only one to have had a totally trouble-free upgrade to 5.2?? I get the
feeling that most everybody seems to have *some* problems...
--
Best Wishes
Sorin
-
http://home-skynet.servehttp.com/
Proud member of TEAM OS/2.
Am Mittwoch, 25. Juni 2008 schrieb [EMAIL PROTECTED]:
Am I the only one to have had a totally trouble-free upgrade to 5.2?? I get
the feeling that most everybody seems to have *some* problems...
Zero problems here after upgrading a bunch of servers. I guess the majority of
users without
Ha, until now it looks ok, but i only upgraded yesterday evening...
On Wed, 25 Jun 2008 12:29:41 +0200
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
sorin.srbu Hi all,
sorin.srbu
sorin.srbu Am I the only one to have had a totally trouble-free upgrade to
5.2?? I get the
sorin.srbu feeling that
[EMAIL PROTECTED] wrote:
Hi all,
Am I the only one to have had a totally trouble-free upgrade to 5.2?? I get the
feeling that most everybody seems to have *some* problems...
well, how it works is that the millions of machines out there where it
just worked, wont get reported, but if things
Andreas Micklei scribbled on Wednesday, June 25, 2008 12:37 PM:
Thank you CentOS team for the good work!
I second that!
smime.p7s
Description: S/MIME cryptographic signature
___
CentOS mailing list
CentOS@centos.org
Karanbir Singh wrote:
[EMAIL PROTECTED] wrote:
Hi all,
Am I the only one to have had a totally trouble-free upgrade to 5.2??
I get the
feeling that most everybody seems to have *some* problems...
well, how it works is that the millions of machines out there where it
just worked, wont get
Karanbir Singh scribbled on Wednesday, June 25, 2008 12:51 PM:
Am I the only one to have had a totally trouble-free upgrade to 5.2?? I
get the feeling that most everybody seems to have *some* problems...
well, how it works is that the millions of machines out there where it
just worked,
[EMAIL PROTECTED] wrote:
Hi all,
Am I the only one to have had a totally trouble-free upgrade to 5.2?? I get the
feeling that most everybody seems to have *some* problems...
Dunc wrote:
[EMAIL PROTECTED] wrote:
Hi all,
Am I the only one to have had a totally trouble-free upgrade to 5.2??
I get the feeling that most everybody seems to have *some* problems...
Hi,
On Wed, 2008-06-25 at 12:29 +0200, [EMAIL PROTECTED] wrote:
Hi all,
Am I the only one to have had a totally trouble-free upgrade to 5.2?? I get
the
feeling that most everybody seems to have *some* problems...
I upgraded 4 machines (all virtual) without any problems from 5.1 to
5.2,
On Wed, 2008-06-25 at 13:30 +0200, [EMAIL PROTECTED] wrote:
Andreas Micklei scribbled on Wednesday, June 25, 2008 12:37 PM:
Thank you CentOS team for the good work!
I second that!
Me too !! And another donation on its way to CentOS ! :)
Regards,
Michel
Johnny Hughes wrote:
If there is something in the conf file that needs to change (that
worked in 5.1 and does not in 5.2) let us know and we can add it to
the release notes and/or wiki.
It was in the listening section as follows:
# A space separated list of IP or host addresses where to
On Wed, 2008-06-25 at 14:39 +0200, Michel van Deventer wrote:
Hi,
snip
I upgraded 4 machines (all virtual) without any problems from 5.1 to
5.2, tonight I'll upgrade the host machine but I do not expect any
problems.
I'm only cautious to upgrade my old webserver which is a dual PIII and
Dunc wrote:
Johnny Hughes wrote:
If there is something in the conf file that needs to change (that
worked in 5.1 and does not in 5.2) let us know and we can add it to
the release notes and/or wiki.
It was in the listening section as follows:
# A space separated list of IP or host
Ned Slider wrote:
That's strange Dunc.
The new config file was written to /etc/dovecot/conf.rpmnew (as
expected) for me, so your modified original doesn't get overwritten. I
can see no difference between the 5.1 and 5.2 config files wrt the
'listen' directive. Mine was, and still is, set to
Dunc wrote:
Hi
Yes it was written as rpmnew, and indeed the default was the same. But
using the original I was using before, changing nothing, with [::] I
could not connect after the upgrade. I restarted many times, and
eventually changing the original to [*] allowed me to connect.
I then
21 matches
Mail list logo