[SCIM] Re: svn malfunction (Re: [immodule-qt] Porting to Qt4)

[LiuCougar]

done. Thanks.

On Wed, 01 Sep 2004 23:45:53 +0900, YamaKen <yamaken at bp.iij4u.or.jp> wrote:
> Hi all, sorry for my long absence.
> 
> Our subversion repository is now suffering unusual deadlock
> problem. Please don't access our repository until the problem
> has been resolved.
> 
> Cougar, Daisuke, please kill following processes to prepare
> resolving.
> 
> yamaken at gabe:~$ ps auxww|grep svn
> cougar   15923  0.3  0.0  5148 1004 ?        S    Aug27  22:24 svnserve.distrib -t
> cougar   15690  0.2  0.0  5144  996 ?        S    Aug28  14:22 svnserve.distrib -t
> daisuke  32587  0.2  0.0  5144  996 ?        S    Aug29  13:07 svnserve.distrib -t
> daisuke  30437  0.2  0.0  2348  628 ?        S    Aug30   7:40 db4.2_deadlock -v -h /svn/immqt/db
> cougar    9578  0.2  0.0  5148  992 ?        S    Aug30   6:07 svnserve.distrib -t
> 
> I've restarted the suspended investigation today, and perhaps
> I've found what is the problem. Thanks Yusuke for the help about
> Linux specific issues.
> 
> There is a permanently locked mutex on mapped shared file
> /svn/immqt/db/__db.001, so other processes are waiting forever,
> even if the process is the deadlock-detecting tool
> db_deadlock. The mutex is not a database itself and usually
> unlocked immediately, so it's not a usual deadlock.
> 
> It will required to restart apache2 to free the locked
> mutex. Following command shows a lot of awaiting apache2
> processes. I'll send the request to admins.
> 
> $ fuser /svn/immqt/db/*
> 
> -------------------------------
> YamaKen  yamaken at bp.iij4u.or.jp
> 
> At Tue, 24 Aug 2004 07:23:53 +0900,
> yamaken at bp.iij4u.or.jp wrote:
> > At Mon, 23 Aug 2004 19:44:50 +0000,
> > liucougar at gmail.com wrote:
> > > I just wonder when we will release next stable patch for Qt 3.3.x ?
> >
> > 2 conditions are remaining.
> >
> > 1. recovery of our svn repository
> > 2. decide some design considerations (waiting for Takumi)
> >
> > Many code fragments have to be backported into Qt3 trunk from
> > Qt4 branch, mainly to make immodule plugins source compatible
> > between Qt3 and Qt4.
> >
> > But our repository is stalling from 2 days ago. Any svn commands
> > that requires server communication are stalled. We cannot
> > update, log, commit, and so on. Only our immodule-qt repository
> > is suffering this unfortune. Other project repository such as
> > uim is working properly.
> >
> > This malfunction cannot be recovered by normal recovery process
> > such as 'svnadmin recover' or 'db_deadlock'. Now I'm in a boring
> > debugging process.
> >
> > my debugging memo (sorry, written in Japanese):
> > http://slashdot.jp/journal.pl?op=display&uid=12605&id=245328
> >
> >
> > Takumi, please reply your opinions to following mails. Otherwise
> > we will go to our own way.
> >
> > ** under discussion (urgent)
> > - introducing QT_IM_SWITCHER environment variable (waiting for Takumi)
> >   http://freedesktop.org/pipermail/immodule-qt/2004-August/000414.html
> >   http://freedesktop.org/pipermail/immodule-qt/2004-August/000416.html
> >
> > ** under discussion
> > - we want something to know available input method names
> >   (waiting for Takumi, Kazuki)
> >   http://freedesktop.org/pipermail/immodule-qt/2004-August/000418.html
> 
> -------------------------------
> YamaKen  yamaken at bp.iij4u.or.jp
> 


-- 
"People's characters are strengthened through struggle against
difficulties; they are weakened by comfort."
- Old Chinese adage