merci pour vos réponses mais je viens de trouver l'origine du
problème:
j'avais un backup d'un ancien /etc dans lequel j'ai vu que le fichier
/etc/network/interfaces contenait:
# This file describes the network interfaces available on your system
# and how to activate them. For more information,
Salut à tous.
Suite à un changement d'architecture, je viens d'installer une lenny à
partir du cd1 amd64.
Mais là, j'ai un problème que je n'avais jamais eu auparavant: je
n'arrive pas à me connecter au localhost de ma machine.
Par exemple, l'interface web de cups est introuvable à l'adresse
steph a écrit :
Salut à tous.
Suite à un changement d'architecture, je viens d'installer une lenny à
partir du cd1 amd64.
Mais là, j'ai un problème que je n'avais jamais eu auparavant: je
n'arrive pas à me connecter au localhost de ma machine.
Par exemple, l'interface web de cups est
Le Wed, Aug 13, 2008 at 01:36:59AM +0200, steph a écrit :
Salut à tous.
Suite à un changement d'architecture, je viens d'installer une lenny à
partir du cd1 amd64.
Mais là, j'ai un problème que je n'avais jamais eu auparavant: je
n'arrive pas à me connecter au localhost de ma machine.
Par
I recently installed Lenny(testing) and I have very few software installed,yet.
I did a nmap scan which showed this:
Interesting ports on localhost (127.0.0.1):
Not shown: 1710 closed ports
PORT STATE SERVICE VERSION
25/tcp open smtp Exim smtpd 4.69
111/tcp open rpcbind
113/tcp
On Wed, Jul 02, 2008 at 01:27:19PM -0700, Luis Maceira wrote:
I recently installed Lenny(testing) and I have very few software
installed,yet.
I did a nmap scan which showed this:
[snip]
the fingerprint above appears that the port 832/tcp is related to privoxy
however when I kill
On Wednesday 02 July 2008 01:27:19 pm Luis Maceira wrote:
I recently installed Lenny(testing) and I have very few software
installed,yet. I did a nmap scan which showed this:
Interesting ports on localhost (127.0.0.1):
Not shown: 1710 closed ports
PORT STATE SERVICE VERSION
25/tcp
Buenas lista.
Siguiendo un artículo he instalado ProFTPd en un debian lenny, con
soporte para TLS, etc.
Todo funciona bien pero lo que no puedo es conectarme desde los equipos
de mi red, solo puedo hacerlo desde el localhost:
Ej. Desde el server donde esta instalado el ftp server puedo
On Wed, May 14, 2008 at 1:41 PM, ciracusa [EMAIL PROTECTED] wrote:
Buenas lista.
Siguiendo un artículo he instalado ProFTPd en un debian lenny, con soporte
para TLS, etc.
Todo funciona bien pero lo que no puedo es conectarme desde los equipos de
mi red, solo puedo hacerlo desde el localhost
desde el localhost:
Ej. Desde el server donde esta instalado el ftp server puedo hacer:
$ ftp localhost
$ ftp 192.168.1.1
Pero desde la red 192.168.1.0/24 no puedo conectarme.
Aclaro que no tengo un firewall en el medio ni Tcpwrappers.
Alguien sabe si debo habilitar alguna opción en el proftpd.conf
conectarme desde los equipos
de mi red, solo puedo hacerlo desde el localhost:
Ej. Desde el server donde esta instalado el ftp server puedo hacer:
$ ftp localhost
$ ftp 192.168.1.1
Pero desde la red 192.168.1.0/24 no puedo conectarme.
Aclaro que no tengo un firewall en el medio ni
funciona bien pero lo que no puedo es conectarme desde los equipos
de mi red, solo puedo hacerlo desde el localhost:
Ej. Desde el server donde esta instalado el ftp server puedo hacer:
$ ftp localhost
$ ftp 192.168.1.1
Pero desde la red 192.168.1.0/24 no puedo conectarme.
Aclaro que no tengo un
Hi,
Can anyone enlighten me as to hows and whys of the way localhost is
implemented in vservers?
I've done a fair bit of reading so now know how to get more than one
vserver's lo interface working by using different 127.0.0.x addresses and
not binding things to 0.0.0.0. But I can't work out why
Selam,
ejabberd'in web admin arayüzüne bağlanamıyor musunuz?
http://ejabberdserver:5280/admin
arayüzünden yönetimi mümkün.
Saygılar.
On Tue, 2008-03-25 at 11:24 +, Zeki ÇATAV wrote:
Merhaba,
Hastanemizde yerel haberleşme ihtiyaçları için önerilerinizle ejabberd
sunucusu debian etch
On Sunday 30 March 2008 17:16:40 Halil Demirezen wrote:
Selam,
ejabberd'in web admin arayüzüne bağlanamıyor musunuz?
http://ejabberdserver:5280/admin
arayüzünden yönetimi mümkün.
Saygılar.
Merhaba,
Lokal makinada bağlanıyor ama LAN'daki başka bir makinadan bağlanmıyor. Sunucu
görevi alan
On Sunday 30 March 2008 23:06:41 Mehmet TURKER wrote:
Ejabberd hiç kullanmadım ama lokal makinede 127.0.0.1 olarak mı
bağlanıyorsunuz ? Eğer öyleyse bir de makine ismiyle deneyin. Makine
ismiyle de LAN daki diğer makinelerden gelir gibi bağlanmıyorsa, aarlardan
olmalı. Bu sorunu Jboss ile
On Monday 31 March 2008 00:12:51 Cahit Güçlü wrote:
Network veya sunucu ayarlarından dolayı bağlanmaya çalıştığınız bu portlar
bloke edilmiş olabilir mi? Basit bir soru gibi görünüyor ama daha önce
benzer bir durum yaşamıştım ve 1 haftaya yakın süre kaynağını arayıp
durmuştum :).
Hastanede
Merhaba,
Hastanemizde yerel haberleşme ihtiyaçları için önerilerinizle ejabberd
sunucusu debian etch üzerinde kurdum. Kurulumda
www.process-one.netadresinden linux-installer dosyasını kullandım.
kvc.tyih.gov.tr adresini kullanarak kurulum yaptım ve conf dosyasında host
olarak bu adres kayıtlı.
Yuksek ihtimal conf dosyasinda disariya acmak icin bir parametre vardir,
dinledigi porta disaridan telnet'le baglanabiliyor musunuz? daemon.log'a da
erisim bilgilerini yaziyor olabilir.
Cok genel oldu ama ejabberd kullanmis birisi daha iyi yorumlayabilir tabi
:),
Ustun
2008/3/25 Zeki ÇATAV
Le 12-03-2008, à 23:20:22 +0100, François TOURDE ([EMAIL PROTECTED]) a écrit :
Lignes : 28
Le 13950ième jour après Epoch,
Steve écrivait:
Le 12-03-2008, à 17:39:53 +0100, François TOURDE ([EMAIL PROTECTED]) a
écrit :
[...]
Tu peux éventuellement inclure une règle iptable qui va
moi qui rêvait de profondeur ..
D'autre part Windows et logiciel libre ne s'excluent pas.
On est d'accord.
Donc sous Windows, j'aurais fait la même chose que sous GNU/Linux : une
redirection du port local 25 avec 6tunnel.
6tunnel -l localhost 25 relais_smtp
Je pensais bien que c'était
6tunnel.
6tunnel -l localhost 25 relais_smtp
--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/DebFrFrenchLists
Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et
Reply-To:
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble
programme en
question utilise la classe PHPMAILER et en regardant dans le code, il
s'attend à trouver un serveur smtp en localhost, ce que je n'ai pas chez
moi. En effet, j'ai viré Postfix au profit de esmtp, qui me
suffit parfaitement pour envoyer mes messages. Le message d'erreur est :
Warning
Le mercredi 12 mars 08 à 16:53, Steve a écrit :
| Bonjour et excusez ce HS.
Bonjour,
[...]
| Warning: fsockopen() [function.fsockopen]: unable to connect to
| localhost:25 (Connection refused) in
/home/steve/local_svn/classes/class.smtp.php on line 105
|
|
| Je me demande maintenant comment
Le 13950ième jour après Epoch,
Steve écrivait:
Le programme en
question utilise la classe PHPMAILER et en regardant dans le code, il
s'attend à trouver un serveur smtp en localhost
Je ne connais pas PHPMAILER, mais il semble dommage qu'il ne soit pas
paramétrable (cherche un fichier genre
Le 12-03-2008, à 17:32:34 +0100, Sébastien NOBILI ([EMAIL PROTECTED]) a écrit :
Lignes : 34
Le mercredi 12 mars 08 à 16:53, Steve a écrit :
| Bonjour et excusez ce HS.
Bonjour,
[...]
| Warning: fsockopen() [function.fsockopen]: unable to connect to
| localhost:25 (Connection
Le 12-03-2008, à 17:39:53 +0100, François TOURDE ([EMAIL PROTECTED]) a écrit :
Lignes : 28
Le 13950ième jour après Epoch,
Steve écrivait:
Le programme en
question utilise la classe PHPMAILER et en regardant dans le code, il
s'attend à trouver un serveur smtp en localhost
Je ne
Le 13950ième jour après Epoch,
Steve écrivait:
Le 12-03-2008, à 17:39:53 +0100, François TOURDE ([EMAIL PROTECTED]) a écrit :
[...]
Tu peux éventuellement inclure une règle iptable qui va renvoyer
l'accès à ton port 25 vers ton serveur smtp habituel.
La solution de seb (voir ma réponse)
I modified some configurations and updated exim4 and when I try sending
get the error message: [error sending: no such host as
localhostoutgoing.verizon.net] I edited /etc/hostname on the local system
to have localhost in it rather than debian too.
--
To UNSUBSCRIBE, email to [EMAIL
On Sat, Feb 09, 2008 at 09:26:27AM -0600, Jude DaShiell wrote:
sample email message cut here:
From [EMAIL PROTECTED]/POP3 Sat Feb 9 10:18:16 2008
Newsgroups: Date: Sat, 9 Feb 2008 10:18:16 -0500 (EST)
From: Jude DaShiell [EMAIL PROTECTED]/POP3
X-X-Sender: [EMAIL PROTECTED]
To: [EMAIL
sample email message cut here:
From [EMAIL PROTECTED]/POP3 Sat Feb 9 10:18:16 2008
Newsgroups:
Date: Sat, 9 Feb 2008 10:18:16 -0500 (EST)
From: Jude DaShiell [EMAIL PROTECTED]/POP3
X-X-Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: test message
Fcc: sent-mail
Message-ID: [EMAIL
On Sat, Feb 09, 2008 at 09:26:27AM -0600, Jude DaShiell wrote:
sample email message cut here:
From [EMAIL PROTECTED]/POP3 Sat Feb 9 10:18:16 2008
Newsgroups: Date: Sat, 9 Feb 2008 10:18:16 -0500 (EST)
From: Jude DaShiell [EMAIL PROTECTED]/POP3
X-X-Sender: [EMAIL PROTECTED]
To: [EMAIL
Kevin,
The /etc/email-addresses wasn't set up properly but whatever is causing
these malformed addresses is overwriting mail user agent headers and is
unaffected by the contents of /etc/email-addresses apparently.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
On Sun, Feb 03, 2008 at 10:40:27AM -0600, Jude DaShiell wrote:
I tried using exim4 and alpine to send a piece of email from one account to
another. I suppose I ought to have given this machine the same domain name
as verizon.net rather than left it at localhost since even with address
I tried using exim4 and alpine to send a piece of email from one account
to another. I suppose I ought to have given this machine the same domain
name as verizon.net rather than left it at localhost since even with
address header rewriting localhost is being prefixed to the proper verizon
I got the following error messageError sending: No such host as
localhostoutgoing.verizon.net]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
In my exim4-config file, I have enabled email headers rewrite enabled but
exim4 says it doesn't hide localhost when I use that feature. I thought
email header rewriting was supposed to be exactly that, a rewrite and a
complete rewrite if necessary. Apparently me and the exim4 team don't see
Jude DaShiell wrote:
I got the following error messageError sending: No such host as
localhostoutgoing.verizon.net]
It looks like strange terminology to me, but you may need a
fullstop/period between localhost and outgoing.
As in: localhost.outgoing.verizon.net
Regards,
David Palmer
as
localhostoutgoing.verizon.net]
It looks like strange terminology to me, but you may need a fullstop/period
between localhost and outgoing.
As in: localhost.outgoing.verizon.net
Regards,
David Palmer.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject
of unsubscribe. Trouble? Contact [EMAIL PROTECTED
Hi,
I am running an RPC call clnt_create(localhost, GET_PRESET,
ADD_VERS, udp) in my C++ program. It gets an error of localhost:
RPC: Program not registered. Does anyone know what I was missing?
Thank you.
Kind Regards,
Jim
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
When you run /sbin/ifconfig is the interface lo up? Are there any
messages in /var/log/syslog that might be relevant?
No, when I run ifconfig, it only gives details for eth1.
There is nothing much in /var/log/syslog
ping -c 2 localhost
ping -c 2 127.0.0.1
# ping -c 2 localhost
PING
El vie, 21-09-2007 a las 08:32 +0100, John O Laoi escribió:
When you run /sbin/ifconfig is the interface lo up? Are there
any
messages in /var/log/syslog that might be relevant?
No, when I run ifconfig, it only gives details for eth1.
There is nothing much in
Have you tried doing 'ifconfig lo up'? If that works try adding a line
like the following to your /etc/network/interfaces:
auto lo
I did just as you suggested above, and it fixed everything.
CUPS is working again, and ifconfig reports lo as well as eth1.
Thanks everyone for your help.
On Fri, 21 Sep 2007 08:32:21 +0100
John O Laoi [EMAIL PROTECTED] wrote:
[...]
# cat /etc/hosts
127.0.0.1 localhost mc
127.0.1.1 mc.home.m mc
[...]
I see that you solved the CUPS problem, but I should point out
that the hosts file above is likely to cause problems elsewhere. You
should
2007/9/21, Liam O'Toole [EMAIL PROTECTED]:
On Fri, 21 Sep 2007 08:32:21 +0100
John O Laoi [EMAIL PROTECTED] wrote:
# cat /etc/hosts
127.0.0.1 localhost mc
127.0.1.1 mc.home.m mc
I see that you solved the CUPS problem, but I should point out
that the hosts file above is likely to cause
On Fri, 21 Sep 2007 12:31:42 +0200
Martin Marcher [EMAIL PROTECTED] wrote:
2007/9/21, Liam O'Toole [EMAIL PROTECTED]:
On Fri, 21 Sep 2007 08:32:21 +0100
John O Laoi [EMAIL PROTECTED] wrote:
# cat /etc/hosts
127.0.0.1 localhost mc
127.0.1.1 mc.home.m mc
I see that you solved
2007/9/21, Liam O'Toole [EMAIL PROTECTED]:
The issue is that 'mc' resolves to 127.0.0.1 (the first match), whereas
mc.home.m resolves to 127.0.1.1 (the only match). Thus the canonical
host name and its alias resolve to different IP addresses.
uh oh, right, reading in context actually helps :)
would not work. (It had been
working well.)
The firefox browser returned the message The server at localhost is taking
too long to respond. when I tried to connect to http://localhost:631.
I also tried http://127.0.0.1:631, and it gave the same responce.
I also could not ping localhost
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
*However, I still can't access CUPS or ping localhost.*
What might be wrong?
Where do I start to look?
When you run /sbin/ifconfig is the interface lo up? Are there any
messages in /var/log/syslog that might be relevant?
Regards,
Tod Detre
On 09/20/2007 02:14 PM, John O Laoi wrote:
[...]
I also could not ping localhost or 127.0.0.1.
So I removed the firewall using
# update-rc.d -f firewall.script remove
and rebooted.
[...]
*However, I still can't access CUPS or ping localhost.*
What might be wrong?
Where do I start to look
OpenSSL).
Pour visualiser l'état d'avancement, je tape alors sur mon navigateur
http://localhost/monsite; , celui-ci me redirige automatiquement vers
https://localhost/monsite;
et ça, y a bien quelqu'un qui l'a configuré, non? si on ne dit pas au
docteur ce qu'on a mangé, il aura du mal à dire
l'état d'avancement, je tape alors sur mon navigateur
http://localhost/monsite; , celui-ci me redirige automatiquement vers
https://localhost/monsite;
puis m'ouvre la fenêtre d'authentification login/password.
Le problème est que maintenant je ne peux plus accéder à mon site, après
visualiser l'état d'avancement, je tape alors sur mon navigateur
http://localhost/monsite; , celui-ci me redirige automatiquement vers
https://localhost/monsite;
puis m'ouvre la fenêtre d'authentification login/password.
Le problème est que maintenant je ne peux plus accéder à mon site, après
Nyizsnyik Ferenc [EMAIL PROTECTED] wrote:
| On Mon, 9 Jul 2007 20:49:14 +0200
| mess-mate [EMAIL PROTECTED] wrote:
|
| Hi,
| i've troubles with my localhost.
| When i do a http://localhost/xxx
| 'requested url was not found' error.
| The server search for http://mydomain.com/xxx
|
| I
mess-mate wrote:
J'avais cru que le site était bien accessible.
As-tu essayé avec firefox ? Tous les ports sont fermé sauf une
redirection du 80.
toujours pas. timeout (testé avec firefox).
--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.net/?DebianFrench
On Wed, Jul 04, 2007 at 05:32:51PM +0200, mouss wrote:
mess-mate wrote:
J'avais cru que le site était bien accessible.
As-tu essayé avec firefox ? Tous les ports sont fermé sauf une
redirection du 80.
toujours pas. timeout (testé avec firefox).
Je viens d'essayer, en effet, rien n'est
On 2007-07-02 21:03:21 +0200, mess-mate wrote:
Le message d'erreur:
[error] [client 127.0.0.1] File does not exist:
/var/www/mondomain.com/nimporte-quoi
C'est pas une question de droit.
Le fichier existe vraiment? Qu'est-ce que donne
ls -l /var/www/mondomain.com
?
--
Vincent Lefèvre
Vincent Lefevre [EMAIL PROTECTED] wrote:
| On 2007-07-02 21:03:21 +0200, mess-mate wrote:
| Le message d'erreur:
| [error] [client 127.0.0.1] File does not exist:
| /var/www/mondomain.com/nimporte-quoi
|
| C'est pas une question de droit.
|
| Le fichier existe vraiment? Qu'est-ce que donne
mess-mate wrote:
[...]
| Le fichier existe vraiment? Qu'est-ce que donne
|
| ls -l /var/www/mondomain.com
|
| ?
|
| --
Biensur, va voir http://www.laplaceverte.fr
Et bien non:
[EMAIL PROTECTED]:~$ telnet www.laplaceverte.fr 80
Trying 86.192.99.224...
et c'est tout. J'avais déjà
Franck Joncourt [EMAIL PROTECTED] wrote:
| On Mon, Jul 02, 2007 at 10:35:58AM +0200, mess-mate wrote:
| Bonjour,
| lors d'un http://localhost/nimporte-quoi
| j'ai toujours le message d'erreurs
| [error] [client 127.0.0.1] File does not exist:
| /var/www/mondomain.com/nimporte-quoi
Daniel Huhardeaux [EMAIL PROTECTED] wrote:
| mess-mate wrote:
| [...]
| | Le fichier existe vraiment? Qu'est-ce que donne
| | | ls -l /var/www/mondomain.com
| | | ?
| | | -- Biensur, va voir http://www.laplaceverte.fr
|
| Et bien non:
|
| [EMAIL PROTECTED]:~$ telnet www.laplaceverte.fr 80
|
Bonjour,
lors d'un http://localhost/nimporte-quoi
j'ai toujours le message d'erreurs
[error] [client 127.0.0.1] File does not exist:
/var/www/mondomain.com/nimporte-quoi
A titre d'information; j'ai un domaine (mondomain.com) activé dans
/etc/apache2/sites-available et sites-enabled.
Et biensur un
Bonjour,
que dit error.log ?
Selon mess-mate [EMAIL PROTECTED]:
Bonjour,
lors d'un http://localhost/nimporte-quoi
j'ai toujours le message d'erreurs
[error] [client 127.0.0.1] File does not exist:
/var/www/mondomain.com/nimporte-quoi
A titre d'information; j'ai un domaine (mondomain.com
On 2007-07-02 10:35:58 +0200, mess-mate wrote:
Bonjour,
lors d'un http://localhost/nimporte-quoi
j'ai toujours le message d'erreurs
[error] [client 127.0.0.1] File does not exist:
/var/www/mondomain.com/nimporte-quoi
A titre d'information; j'ai un domaine (mondomain.com) activé dans
/etc
On Mon, Jul 02, 2007 at 10:35:58AM +0200, mess-mate wrote:
Bonjour,
lors d'un http://localhost/nimporte-quoi
j'ai toujours le message d'erreurs
[error] [client 127.0.0.1] File does not exist:
/var/www/mondomain.com/nimporte-quoi
A titre d'information; j'ai un domaine (mondomain.com) activé
BOUIDA Djelloul [EMAIL PROTECTED] wrote:
| Bonjour,
|
| que dit error.log ?
|
| Selon mess-mate [EMAIL PROTECTED]:
|
| Bonjour,
| lors d'un http://localhost/nimporte-quoi
| j'ai toujours le message d'erreurs
| [error] [client 127.0.0.1] File does not exist:
| /var/www/mondomain.com
On Sat, Mar 03, 2007 at 01:59:15PM +0100, Joe Hart wrote :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Delalleau wrote:
Hello debianers!
For some reason I can no longer ping localhost:
ping -c 3 localhost
PING localhost.localdomain (127.0.0.1) 56(84) bytes of data
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Delalleau wrote:
Hello debianers!
For some reason I can no longer ping localhost:
ping -c 3 localhost
PING localhost.localdomain (127.0.0.1) 56(84) bytes of data.
--- localhost.localdomain ping statistics ---
3 packets transmitted, 0
Bruno Delalleau wrote:
Hello debianers!
For some reason I can no longer ping localhost:
ping -c 3 localhost
PING localhost.localdomain (127.0.0.1) 56(84) bytes of data.
--- localhost.localdomain ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2000ms
I saw
Hello debianers!
For some reason I can no longer ping localhost:
ping -c 3 localhost
PING localhost.localdomain (127.0.0.1) 56(84) bytes of data.
--- localhost.localdomain ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2000ms
I saw that when I tried to configure
Hi!
My squid (2.5.9-10sarge2) is sending this error:
WARNING: rejecting 'localhost' as a name server, because it is not a numeric IP
address
He's working fine, but I want to correct this error.
Have anyone see this error before? Any suggestions?
Thks!
[]s
Antonio
--
To UNSUBSCRIBE, email
On Fri, 01 Dec 2006 11:01:38 -0200
Antonio Felipe [EMAIL PROTECTED] wrote:
Hello Antonio,
WARNING: rejecting 'localhost' as a name server, because it is not a
He's working fine, but I want to correct this error.
Have anyone see this error before? Any suggestions?
Why not replace localhost
Hi,
On Sun, Nov 12, 2006 at 11:28:45PM +0200, Hans du Plooy wrote:
Hi guys,
Just wondering, which is correct:
127.0.0.1localhost.localdomainlocalhost
or
127.0.0.1localhost
The linux networking howto
(http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html) muddies
On Tue, Nov 21, 2006 at 07:51:49PM -0500, Douglas Tutty wrote:
On Wed, Nov 22, 2006 at 12:17:03AM +0100, Vincent Lefevre wrote:
On 2006-11-21 15:49:07 +0100, Matus UHLAR - fantomas wrote:
Indeed your hosts.allow probably wasn't complete. In addition to
localhost, you should have added
On Sat 2006-11-25 23:58:42 +1300, Chris Bannister wrote:
On Tue, Nov 21, 2006 at 07:51:49PM -0500, Douglas Tutty wrote:
I've had stand-alone (aka secure) boxes called localhost, with only the
standard 127.0.0.1 /etc/hosts entry. Never had a problem.
Never tried to install leafnode
On Sat, 2006-11-25 at 11:03 +, David Hart wrote:
On Sat 2006-11-25 23:58:42 +1300, Chris Bannister wrote:
On Tue, Nov 21, 2006 at 07:51:49PM -0500, Douglas Tutty wrote:
I've had stand-alone (aka secure) boxes called localhost, with only the
standard 127.0.0.1 /etc/hosts entry
/hostname to jim, rebooted, and was greeted with
jim login:
The hostname command gave me jim.
On the other hand, I changed the /etc/hosts entry to
127.0.0.1 tom dick harry quash localhost loopback
to see what would happen. It had no effect on hostname. The only
problem I've had so far
/hostname file. I changed the entry in
/etc/hostname to jim, rebooted, and was greeted with
jim login:
The hostname command gave me jim.
On the other hand, I changed the /etc/hosts entry to
127.0.0.1 tom dick harry quash localhost loopback
to see what would happen. It had
that requests it (I
don't think there's another portable way to fully identify the
machine).
I've had stand-alone (aka secure) boxes called localhost, with only
the standard 127.0.0.1 /etc/hosts entry. Never had a problem.
You haven't seen any problem, but this doesn't mean
On 2006-11-22 13:41:22 +0100, David Jardine wrote:
On Wed, Nov 22, 2006 at 12:17:03AM +0100, Vincent Lefevre wrote:
Well, the result of the hostname command depends on the /etc/hosts
file and if your configuration is incorrect, it may not give you a
consistent result.
Not here. It
On Wed, Nov 22, 2006 at 12:17:03AM +0100, Vincent Lefevre wrote:
On 2006-11-21 15:49:07 +0100, Matus UHLAR - fantomas wrote:
Indeed your hosts.allow probably wasn't complete. In addition to
localhost, you should have added the hostname. Or perhaps the IP
address 127.0.0.1.
there often
problems was having localhost in hosts.allow or similar
files, which didn't match when 127.0.0.1 mapped to something else.
Indeed your hosts.allow probably wasn't complete. In addition to
localhost, you should have added the hostname. Or perhaps the IP
address 127.0.0.1.
there often is no FQDN
Am 2006-11-13 02:07:52, schrieb David Jardine:
To muddy the water a little more, I have
127.0.0.1 quash localhost loopback
This is definitivly wrong!
An /etc/hosts file can have only 3 fields plus comment.
It should be
127.0.0.1 localhost localhost
Michelle Konzack wrote:
Am 2006-11-13 02:07:52, schrieb David Jardine:
To muddy the water a little more, I have
127.0.0.1 quash localhost loopback
This is definitivly wrong!
An /etc/hosts file can have only 3 fields plus comment.
It should be
127.0.0.1
On Sun, Nov 19, 2006 at 03:14:48PM +0100, Michelle Konzack wrote:
An /etc/hosts file can have only 3 fields plus comment.
Who says?
--
David Jardine
Running Debian GNU/Linux and
loving every minute of it. -L. von Sacher-M.(1835-1895)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Am 2006-11-13 02:07:52, schrieb David Jardine:
To muddy the water a little more, I have
127.0.0.1 quash localhost loopback
On 19.11.06 15:14, Michelle Konzack wrote:
This is definitivly wrong!
An /etc/hosts file can have only 3 fields plus comment.
no, there may be more
other IP address),
you should write
127.0.0.1 fnote.local fnote localhost
(well, fnote.local isn't even a correct FQDN, IMHO). I don't think
127.0.0.1 should necessarily be reversed as localhost; what is
important is that localhost should resolve as 127.0.0.1, and this
is OK with the above
)
bugreport: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=345761
The hosts man page is clear. You should write
IP_address canonical_hostname [aliases...]
So, in your case (as your machine doesn't have any other IP address),
you should write
127.0.0.1 fnote.local fnote localhost
(well, fnote.local
On 13.11.06 13:21, Vincent Lefevre wrote:
On 2006-11-13 10:48:12 +0100, Matus UHLAR - fantomas wrote:
some time ago I was pondering about this issue, because having
'fnote' (name of by notebook) as first caused problems with some
services expecting 127.0.0.1 to map to localhost (which
On 12.11.06 23:28, Hans du Plooy wrote:
Just wondering, which is correct:
127.0.0.1localhost.localdomainlocalhost
or
127.0.0.1localhost
I think that the second one is correct. Imho, 127.0.0.1 should always map to
'localhost' without domain, even if some other
On Mon, Nov 13, 2006 at 02:07:52AM +0100, David Jardine wrote:
To muddy the water a little more, I have
127.0.0.1 quash localhost loopback
where quash is the name of the machine. I don't remember how I came
to do this, but it must have been from some debian documentation
Hans du Plooy wrote:
127.0.0.1localhost.localdomainlocalhost
This is the default Debian configuration, but it is a good
question as to why it is necessary.
You have to use hostname.domainhostname format for a real
hostname and domain, but what is the point
On 2006-11-13 10:48:12 +0100, Matus UHLAR - fantomas wrote:
some time ago I was pondering about this issue, because having
'fnote' (name of by notebook) as first caused problems with some
services expecting 127.0.0.1 to map to localhost (which is imho a
MUST), and 'hostname -s' returned
On Sun, Nov 12, 2006 at 08:57:01PM -0500, Douglas Tutty wrote:
On Mon, Nov 13, 2006 at 02:07:52AM +0100, David Jardine wrote:
To muddy the water a little more, I have
127.0.0.1 quash localhost loopback
where quash is the name of the machine. I don't remember how I came
Hi guys,
Just wondering, which is correct:
127.0.0.1localhost.localdomainlocalhost
or
127.0.0.1localhost
The linux networking howto
(http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html) muddies the water even
more:
127.0.0.1 localhost loopback
I was always under
On Sun, Nov 12, 2006 at 11:28:45PM +0200, Hans du Plooy wrote:
Hi guys,
Just wondering, which is correct:
127.0.0.1localhost.localdomainlocalhost
I was always under the impression the first is the proper way. I seem
to be having issues with resovling localhost
On Sun, Nov 12, 2006 at 11:28:45PM +0200, Hans du Plooy wrote:
Hi guys,
Just wondering, which is correct:
127.0.0.1localhost.localdomainlocalhost
or
127.0.0.1localhost
The linux networking howto
(http://www.tldp.org/HOWTO/NET3-4-HOWTO-5.html) muddies
On Mon, Nov 13, 2006 at 02:07:52AM +0100, David Jardine wrote:
To muddy the water a little more, I have
127.0.0.1 quash localhost loopback
where quash is the name of the machine. I don't remember how I came
to do this, but it must have been from some debian documentation
On Sun, 2006-11-12 at 17:15 -0500, Douglas Tutty wrote:
On Sun, Nov 12, 2006 at 11:28:45PM +0200, Hans du Plooy wrote:
127.0.0.1localhost.localdomainlocalhost
I was always under the impression the first is the proper way. I seem
to be having issues with resovling
Moin,
* Klaus Becker wrote (2006-11-01 19:49):
http://127.0.0.1 funktionniert bei mir, localhost aber nicht.
Dabei steht in /etc/hosts u. A.:
127.0.0.1 localhost.localdomain localhost
^
Das sollte raus. Bisher hat mir noch niemand erklären können
401 - 500 of 1065 matches
Mail list logo
