Mercurial > hg > mercurial-crew
view tests/test-inotify-issue1208.t @ 18096:cd53e40ab0e2
inotify: don't fall over just because of a dangling symlink
Previously, the inotify server failed to start if .hg/inotify.sock was
a symlink that pointed to a non-existent path. This behaviour does not
seem to make any sense.
Now, if we encounter a broken symlink, we unlink it and continue.
author | Bryan O'Sullivan <bryano@fb.com> |
---|---|
date | Tue, 18 Dec 2012 17:33:32 -0800 |
parents | f2719b387380 |
children |
line wrap: on
line source
$ "$TESTDIR/hghave" inotify || exit 80 $ echo "[extensions]" >> $HGRCPATH $ echo "inotify=" >> $HGRCPATH $ p="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" $ hg init $p $ cd $p dangling symlink should be deleted $ ln -sf doesnotexist .hg/inotify.sock $ hg --config inotify.pidfile=../hg.pid st $ kill `cat ../hg.pid` inserve $ hg inserve -d --pid-file=hg.pid $ cat hg.pid >> "$DAEMON_PIDS" status $ hg status ? hg.pid if we try to start twice the server, make sure we get a correct error $ hg inserve -d --pid-file=hg2.pid abort: inotify-server: cannot start: socket is already bound abort: child process failed to start [255] $ kill `cat hg.pid` $ cd ..