After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 44573 - gethostbyname calls have no timeout
gethostbyname calls have no timeout
Status: RESOLVED WONTFIX
Product: gnome-vfs
Classification: Deprecated
Component: Other
cvs (head)
Other All
: Normal normal
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2000-11-06 21:20 UTC by Darin Adler
Modified: 2008-09-06 19:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Darin Adler 2001-09-10 00:45:25 UTC
They rely on the underlying TCP timeout which can be truly huge. This is
probably not acceptable, since the gnome-vfs caller has no way to do the
traditional SIGALRM timeout explicitly.



------- Additional Comments From mikef@praxis.etla.net 2000-11-07 12:47:45 ----

This looks like it'll be hard to fix right.



------- Additional Comments From mikef@praxis.etla.net 2000-12-05 16:50:30 ----

This is a lot of work and I'm not clear on what the detrimental effect on the
user experience is.

I believe that the UI won't block, since these gethostbyname requests happen in
separate threads.

I don't think we can fix this in 1.0 anyway; perhaps the most we should do is
make sure that there are no catastrophic bugs that appear when Nautilus is used
when a network connection is enabled but not actually connected.




------- Additional Comments From eli@eazel.com 2001-02-16 15:10:49 ----

Currently, if you yank your network connection and try to use embedded Mozilla,
Nautilus will be completely hung; you can only kill it from a command line.



------- Additional Comments From mikef@praxis.etla.net 2001-02-17 14:12:35 ----

See also 6390



------- Additional Comments From don@eazel.com 2001-02-20 08:52:46 ----

Isn't bug #46390 a duplicate of this?




------- Additional Comments From don@eazel.com 2001-02-20 08:57:30 ----

Undeferring this.  It looks like there can be a big user-visible problem here.




------- Additional Comments From mikef@praxis.etla.net 2001-02-20 13:04:40 ----

I think the correct fix to this is to fix 6790, not to fix this bug.



------- Additional Comments From mikef@praxis.etla.net 2001-02-20 13:05:17 ----

I meant 6390



------- Additional Comments From mikef@praxis.etla.net 2001-02-20 16:54:00 ----

I'm marking this P6 without a milestone so that it can be moved back into
deferred.
We will fix 6390 but not the specific issue discussed in this bug.  Fixing 6390
will resolve the user-visible effects of this bug.



------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 20:45 -------
Comment 1 Allison Karlitskaya (desrt) 2004-08-13 04:24:02 UTC
HTTP no longer uses gethostbyname().

gethostbyname() is, however, used by libgnomevfs (gnome_vfs_resolve) and this is
still a problem.
Comment 2 Christian Neumair 2005-05-07 07:10:15 UTC
We currently use gethostname() in
modules/cdda-cddb.c:CDDBConnect
modules/nfs-methoc.c:server_connection_acquire
imported/neon/ne_socket.c:ne_addr_resolve (if USE_GETADDRINFO is not defined)
libgnomevfs/gnome-vfs-resolve.c:gnome_vfs_resolve (also uses gethostbyname_r)

Maybe somebody with more knowledge of these internals could look at this?
Comment 3 Christian Neumair 2005-05-07 07:14:20 UTC
Or maybe we can have something like wget:
http://www.gzlinux.org/lxr/http/ident?i=gethostbyname_with_timeout
Comment 4 André Klapper 2008-09-06 19:17:27 UTC
gnome-vfs has been deprecated and superseded by gio/gvfs since GNOME 2.22, hence mass-closing many of the gnome-vfs requests/bug reports. This means that gnome-vfs is NOT actively maintained anymore, however patches are still welcome.

If your reported issue is still valid for gio/gvfs, please feel free to file a bug report against glib/gio or gvfs.

@Bugzilla mail recipients: query for gnome-vfs-mass-close to get rid of these notification emails all together.


General further information: http://en.wikipedia.org/wiki/GVFS 
Reasons behind this decision are listed at http://www.mail-archive.com/gnome-vfs-list@gnome.org/msg00899.html