screen do not lock serial port

Bug #13211 reported by Alexandra Kossovsky on 2005-02-23
4
Affects Status Importance Assigned to Milestone
screen
Unknown
Unknown
screen (Ubuntu)
Medium
Unassigned

Bug Description

I use screen to connect to serial ports: "screen /dev/ttyS0". If there is
minicom running, it does not allow to run second minicom by using
/var/lock/LCK..ttyS0 lock file. screen does not look on this lock file and it is
possible to run minicom and after that to run screen with the same serial port.

Matt Zimmerman (mdz) wrote :

This should probably go upstream

Changed in screen:
assignee: nobody → dsilvers
status: Unconfirmed → Confirmed
Daniel Silverstone (dsilvers) wrote :

This is now upstream at https://savannah.gnu.org/bugs/?func=detailitem&item_id=16661

Since we cannot watch savannah bugs yet, I have not added a proper bug watch

Changed in screen:
assignee: dsilvers → nobody
Christian Reis (kiko) on 2008-03-01
Changed in screen:
importance: Undecided → Unknown
status: New → Unknown

Thank you for posting this bug.

Does this occur in Lucid?

Changed in screen (Ubuntu):
status: Confirmed → Incomplete

closing as it should have automatically invalidated 60 days after inactivity in the incomplete stage.

Changed in screen (Ubuntu):
status: Incomplete → Invalid
Axel Beckert (xtaran) wrote :

Still the case in precise.

It though emits a short warning message if there's already a minicom using the same port:

SetTTY (fd 6): ioctl failed: Interrupted system call

Changed in screen (Ubuntu):
status: Invalid → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.