[Bug 661749] New: minicom does not work with unix sockets because of lockdev
https://bugzilla.novell.com/show_bug.cgi?id=661749 https://bugzilla.novell.com/show_bug.cgi?id=661749#c0 Summary: minicom does not work with unix sockets because of lockdev Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ag@pre-secure.de QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 minicom allows you to connect to unix sockets by specifying "unix#" at the beginning of the device name. (i.e. "unix#/path/to/my/socket"). from the minicom man page: "To use a UNIX socket for communication the device name must be prefixed with "unix#" following by the full path and the filename of the socket. Minicom will then try to connect to this socket as a client." but the path is passed to lockdev with the prefix causing lockdev to fail. also, locking cannot be disabled anymore. neither by using the command line option "-o" for which the man page states that: "no check for lock files" neither by using none or an invalid locking directory. from the man page again: "If this directory does not exist, minicom will not attempt to use lockfiles." a short excerpt from an strace (i edited the socket names): [pid 2254] execve("/usr/sbin/lockdev", ["/usr/sbin/lockdev", "-l", "unix#/path/to/socket"], . [pid 2254] stat("/dev/unix#/path/to/socket", 0x7fff8d605070) = -1 ENOENT (No such file or directory) minicom execs lockdev but passes the full socket name without removing the "unix#" prefix first. from the changelog in the minicom src-rpm * Tue Mar 9 2010 lnussel@suse.de - use lockdev (FATE#308360) Reproducible: Always Steps to Reproduce: 1. specify any socet in the minicom setup with a "unix#" prefix 2. restart minicom 3. Actual Results: error message: Device unix#/path/to/socket access failed: No such file or directory. Expected Results: - minicom working with sockets - correct documentation about how to control locking -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=661749 https://bugzilla.novell.com/show_bug.cgi?id=661749#c Marcus Meissner <meissner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|anicka@novell.com |lnussel@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=661749 https://bugzilla.novell.com/show_bug.cgi?id=661749#c2 Ludwig Nussel <lnussel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Target Milestone|--- |Factory --- Comment #2 from Ludwig Nussel <lnussel@novell.com> 2011-01-11 16:59:10 CET --- socket support isn't actually compiled in. Fixed for 11.4. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com