Brian wrote:
Bob Proulx wrote:
Brian wrote:
or, if the domain name is left blank,
127.0.1.1 foo
would be seen.
Doesn't it create an entry like this? I will need to test it in order
to see what it creates in that case.
127.0.1.1 foo.localdomain foo
I will
On Fri 13 Jun 2014 at 15:28:48 -0600, Bob Proulx wrote:
Brian wrote:
Bob Proulx wrote:
Brian wrote:
True. What do think about the lack of '127.0.1.1 localhost' in
It is the 127.0.1.1 localhost to which I was disagreeing. That
would be unusual. It is still the loopback device so
On Thu 12 Jun 2014 at 16:23:37 -0600, Bob Proulx wrote:
Brian wrote:
Tom H wrote:
Brian wrote:
Teresa e Junior wrote:
$ cat /etc/hostname
localhost
...
True. What do think about the lack of '127.0.1.1 localhost' in
etc/hosts? Squeeze and Wheezy installs would both put
Brian wrote:
Bob Proulx wrote:
Brian wrote:
True. What do think about the lack of '127.0.1.1 localhost' in
It is the 127.0.1.1 localhost to which I was disagreeing. That
would be unusual. It is still the loopback device so off the top of
my head I think everything should still work okay.
Brian wrote:
Tom H wrote:
Brian wrote:
Teresa e Junior wrote:
$ cat /etc/hostname
localhost
...
True. What do think about the lack of '127.0.1.1 localhost' in
etc/hosts? Squeeze and Wheezy installs would both put this line in.
Process check! I think you have mixed up the two
On Tue, 10 Jun 2014 08:22:58 +0300, Andrei POPESCU wrote:
As far as I can tell mpc is low-level enough to not care about what
Network Manager advertises. I'm suspecting it does have something to do
with DNS, so I'd suggest you pick a name for your machine and make sure
you adjust your configs as
On Mon, 9 Jun 2014 09:53:31 +0400, Reco wrote:
Your network configuration may be the cause of this. Can you please run
mpc like this, and show the result:
strace -e trace=network mpc
$ strace -e trace=network mpc
socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
connect(3,
On Mon, 09 Jun 2014 02:02:02 -0400
Teresa e Junior teresaejun...@gmail.com wrote:
On Mon, 9 Jun 2014 09:53:31 +0400, Reco wrote:
Your network configuration may be the cause of this. Can you please run
mpc like this, and show the result:
strace -e trace=network mpc
$ strace -e
On Mon, 9 Jun 2014 10:30:09 +0400, Reco wrote:
So, mpc tries standard mpd socket and fails. Adding said socket to
mpd.conf (via bind_address) should solve the issue.
Just adding a path to the socket doesn't really solve the issue (I run
MPD as my user, so there is no access to /var/run). I
On Mon, Jun 09, 2014 at 03:16:00AM -0400, Teresa e Junior wrote:
On Mon, 9 Jun 2014 10:30:09 +0400, Reco wrote:
So, mpc tries standard mpd socket and fails. Adding said socket to
mpd.conf (via bind_address) should solve the issue.
Just adding a path to the socket doesn't really solve the
On Mon, 9 Jun 2014 11:49:15 +0400, Reco wrote:
Ok. Thinking about it, I beleive I may miss something. What does show:
strace -f mpc
OK, the first log is from when it fails, and the second from when the
Wifi is connected. You'll see it reads from /etc/hosts more than just
127.0.0.1
On Mon 09 Jun 2014 at 01:23:43 -0400, Teresa e Junior wrote:
$ cat /etc/hostname
localhost
I wouldn't use this in /etc/hostname. Contacting this machine from
elsewhwere on the network could prove frustrating.
$ cat /etc/hosts
127.0.0.1 localhost
This line is the complete contents of
On Lu, 09 iun 14, 01:23:43, Teresa e Junior wrote:
Hello to all!
I've had this problem with previous versions of MPD, and now I'm using
0.18.7, but the problem persists. This is an odd situation: MPD is
configured to run on 127.0.0.1, but if the Wifi is disconnected in
NetworkManager, it
On Mon, Jun 09, 2014 at 04:04:21AM -0400, Teresa e Junior wrote:
On Mon, 9 Jun 2014 11:49:15 +0400, Reco wrote:
Ok. Thinking about it, I beleive I may miss something. What does show:
strace -f mpc
OK, the first log is from when it fails, and the second from when
the Wifi is connected.
On Mon, 9 Jun 2014 09:55:06 +0100, Brian wrote:
On Mon 09 Jun 2014 at 01:23:43 -0400, Teresa e Junior wrote:
$ cat /etc/hostname
localhost
I wouldn't use this in /etc/hostname. Contacting this machine from
elsewhwere on the network could prove frustrating.
I think that is or was a basic
On Mon, Jun 9, 2014 at 4:55 AM, Brian a...@cityscape.co.uk wrote:
On Mon 09 Jun 2014 at 01:23:43 -0400, Teresa e Junior wrote:
$ cat /etc/hostname
localhost
I wouldn't use this in /etc/hostname. Contacting this machine from
elsewhwere on the network could prove frustrating.
The hostname in
On Mon 09 Jun 2014 at 07:58:41 -0400, Tom H wrote:
On Mon, Jun 9, 2014 at 4:55 AM, Brian a...@cityscape.co.uk wrote:
On Mon 09 Jun 2014 at 01:23:43 -0400, Teresa e Junior wrote:
$ cat /etc/hostname
localhost
I wouldn't use this in /etc/hostname. Contacting this machine from
On Mon, 9 Jun 2014 11:56:25 +0300, Andrei POPESCU wrote:
Could you please post the output of 'ip a' after you disconnect the
WiFi?
Just in case, I'm posting the output of both when the Wifi is off and on:
$ ip a
1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN
On Mon, 9 Jun 2014 13:27:21 +0400, Reco wrote:
Weird. Just weird. Try it like this:
1) Start as root:
/usr/sbin/tcpdump -nn -i any udp port 53 or udp port 5353
2) Run mpc in another shell.
3) Please post the contents of your /etc/nsswitch.conf
Nothing really happens in the tcpdump window
On Mon, Jun 9, 2014 at 8:10 AM, Brian a...@cityscape.co.uk wrote:
On Mon 09 Jun 2014 at 07:58:41 -0400, Tom H wrote:
On Mon, Jun 9, 2014 at 4:55 AM, Brian a...@cityscape.co.uk wrote:
On Mon 09 Jun 2014 at 01:23:43 -0400, Teresa e Junior wrote:
$ cat /etc/hostname
localhost
I wouldn't use
On Mon, Jun 9, 2014 at 8:39 AM, Teresa e Junior teresaejun...@gmail.com wrote:
$ sudo /usr/sbin/tcpdump -nn -i any udp port 53 or udp port 5353
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535
On Mon, Jun 9, 2014 at 9:58 PM, Tom H tomh0...@gmail.com wrote:
On Mon, Jun 9, 2014 at 4:55 AM, Brian a...@cityscape.co.uk wrote:
On Mon 09 Jun 2014 at 01:23:43 -0400, Teresa e Junior wrote:
$ cat /etc/hostname
localhost
I wouldn't use this in /etc/hostname. Contacting this machine from
I believe it's got something to do with NetworkManager, because mpc
started working as soon as I run:
$ sudo service network-manager stop
And then I run this, and while trying to connect, or later if connecting
fails, mpc won't work again:
$ sudo service network-manager start
The version of
On Lu, 09 iun 14, 23:05:43, Teresa e Junior wrote:
I believe it's got something to do with NetworkManager, because mpc started
working as soon as I run:
$ sudo service network-manager stop
And then I run this, and while trying to connect, or later if connecting
fails, mpc won't work again:
Hello to all!
I've had this problem with previous versions of MPD, and now I'm using
0.18.7, but the problem persists. This is an odd situation: MPD is
configured to run on 127.0.0.1, but if the Wifi is disconnected in
NetworkManager, it starts spitting error messages and refuses to play:
$
Hi.
On Mon, 09 Jun 2014 01:23:43 -0400
Teresa e Junior teresaejun...@gmail.com wrote:
I have asked for help at http://forum.musicpd.org/, but they said
something is not right in my network, and I believe that could be
actually the case.
Your network configuration may be the cause of this.
26 matches
Mail list logo
