On 7/15/14, Jiri Bourek bou...@thinline.cz wrote:
On 15.7.2014 11:13, Nick Edwards wrote:
On 7/14/14, Jiri Bourek bou...@thinline.cz wrote:
On 14.7.2014 00:24, Nick Edwards wrote:
On 7/12/14, Steve Litt sl...@troubleshooters.com wrote:
experience with Debian Wheezy is that lo goes down a
On 7/14/14, Jiri Bourek bou...@thinline.cz wrote:
On 14.7.2014 00:24, Nick Edwards wrote:
On 7/12/14, Steve Litt sl...@troubleshooters.com wrote:
experience with Debian Wheezy is that lo goes down a lot, so this is
one of the first things I do when odd stuff happens.
Use a better operating
On 15.7.2014 11:13, Nick Edwards wrote:
On 7/14/14, Jiri Bourek bou...@thinline.cz wrote:
On 14.7.2014 00:24, Nick Edwards wrote:
On 7/12/14, Steve Litt sl...@troubleshooters.com wrote:
experience with Debian Wheezy is that lo goes down a lot, so this is
one of the first things I do when odd
On 07/12/2014 01:41 PM, Reindl Harald wrote:
Am 12.07.2014 13:31, schrieb Steve Litt:
A malfunctioning lo will cause Dovecot not to connect to clients. My
experience with Debian Wheezy is that lo goes down a lot, so this is
one of the first things I do when odd stuff happens
uhm if you
On 7/12/14, Steve Litt sl...@troubleshooters.com wrote:
experience with Debian Wheezy is that lo goes down a lot, so this is
one of the first things I do when odd stuff happens.
Use a better operating system then, I've used at work and home, suse,
opensuse, rhel, centos, slackware and
On 14.7.2014 00:24, Nick Edwards wrote:
On 7/12/14, Steve Litt sl...@troubleshooters.com wrote:
experience with Debian Wheezy is that lo goes down a lot, so this is
one of the first things I do when odd stuff happens.
Use a better operating system then
Blaming operating system after *one*
Nick Edwards nick.z.edwa...@gmail.com wrote:
On 7/12/14, Steve Litt sl...@troubleshooters.com wrote:
experience with Debian Wheezy is that lo goes down a lot, so this
is one of the first things I do when odd stuff happens.
Use a better operating system then, I've used at work and home, suse,
Hi all,
You probably know this already, but just in case...
Let's say you have your email client getting mail from a Dovecot server
on the same computer (which is a really good way of doing things, by
the way). Then one day your email client starts saying connection
refused after a suitably long
Am 12.07.2014 13:31, schrieb Steve Litt:
ifdown lo
ifup lo
A malfunctioning lo will cause Dovecot not to connect to clients. My
experience with Debian Wheezy is that lo goes down a lot, so this is
one of the first things I do when odd stuff happens
uhm if you *loopback device* goes down
