Re: [Gnu-arch-users] [BUG] a socket file in the way causes 'tla inventory' panic

[Matthieu MOY]

Quoting Jan Hudec <address@hidden>:

> Just like for directories and symlinks tla does not try to read the id
> from the file and instead looks for an explicit one, neither should it
> with pipes, sockets and devices.

I'm not sure to understand your answer. It *should* not try to read, but it
actually does:

$ strace tla inventory
[ ... ]
lstat64("./socket", {st_mode=S_IFSOCK|0755, st_size=0, ...}) = 0
open("./.arch-ids/socket.id", O_RDONLY) = -1 ENOENT (No such file or directory)
open("./.arch-ids/=all", O_RDONLY)      = -1 ENOENT (No such file or directory)
open("./socket", O_RDONLY)              = -1 ENXIO (No such device or address)
write(2, "error finding file id (", 23error finding file id () = 23

The last "open" is an attempt to find the tagline, isn't it ?

> Note, however, that socket nodes should
> never exist unless the application is running, since bind insists on
> creating them.

I use an application which lets a socket in my working directory even after
exiting. It's not my application, but I don't want it to disturb my work anyway.

-- 
Matthieu

-------------------------------------------------
envoyé via Webmail/IMAG !