[Xastir] Xastir on Mepis - ttyS0 hard fail

[James Washer]

see 'man lsof'


On 08 Feb 2004 14:35:46 -0500
Gale Wilkinson <gdwrbw at ftc-i.net> wrote:

> I checked and /dev/mouse is pointing to /dev/input/mice.  
> 
> My next question in this case is:  Is there some nice little program
> that I could use to see if/what is using ttyS0 at any given time?  I am
> fairly new to Linux and am not sure how to track down what is actually
> locking the port for me...
> 
>      Gale
> 
> On Sun, 2004-02-08 at 12:55, Matt Werner wrote:
> > ----- Original Message ----- 
> > From: "J. Lance Cotton" <joe at lightningflash.net>
> > To: "Gale Wilkinson" <gdwrbw at ftc-i.net>
> > Cc: <xastir at xastir.org>
> > Sent: Sunday, February 08, 2004 10:16 AM
> > Subject: Re: [Xastir] Xastir on Mepis - ttyS0 hard fail
> > 
> > 
> > > That sounds like something else has opened the serial port. When you start
> > > Xastir as a normal user, it is finding the lockfile put there by whatever
> > > program is already using the port. When you start as root, it can
> > overwrite
> > > the file, but that doesn't change the fact that the port is open by some
> > > other program, which is causing your hard fails.
> > >
> > > Look to see if some other program is using the serial port, maybe a getty
> > > login thread or serial console.
> > 
> > I've found that gpm, the mouse daemon, can be a good one for this.  Make
> > sure /dev/mouse doesn't point to your serial port.
> > 
> > 73 - Matt
> > 
> > _______________________________________________
> > Xastir mailing list
> > Xastir at xastir.org
> > https://krypton.hscs.virginia.edu/mailman/listinfo/xastir
> 
> _______________________________________________
> Xastir mailing list
> Xastir at xastir.org
> https://krypton.hscs.virginia.edu/mailman/listinfo/xastir
>