kicad-developers team mailing list archive

[Henner Zeller <h.zeller@xxxxxxx>]

On 7 February 2014 10:42, Lorenzo Marcantonio
<l.marcantonio@xxxxxxxxxxxx> wrote:
> Got tired of all the lockfiles in the home directory, tried to look at
> the issue. Sadly is (almost) everything in wxWidgets.

FYI, I found the same thing and filed a patch with the wxWidgets
people a couple of days ago.
Looks like they just applied it:

http://trac.wxwidgets.org/ticket/15944

.. however, this probably will only make it into the 3.x version, so
might take some time until it will generally be available.

>
> It doesn't even catch SIGTERM so a shutdown or ^C or whatever else don't
> cleanup them.

I think we should have signal handlers that deletes the singleton
instance to clean up the mess^H^H^H^HLockfile

>
> Solution: ripped out the lockfile logic from my branch :P
>
> Question: do we really need them? IIRC they were only for coordinating
> the eeschema/pcbnew IPC (and it's a confirmation only). Data files are
> only read/written in a single go, not kept open as a db. Since locks are
> in the home it doesn't even guard over NFS (or other file sharing
> mechanism). The worst? You overwrite modification you did in another
> instance. We could eventually warn for this comparing filestamps (vim
> does it that way).

I think we should switch to some IPC mechanism (e.g. something over a
UNIX domain socket in Unix) to transfer
some basic information between programs. E.g. would send an event to
CvPcb to fetch a new netist etc. Might be
worth considering.

-h

>
> Now I'm working happier:D did I miss some fatal flaw?
>
> --
> Lorenzo Marcantonio
> Logos Srl
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp