is it necessary to svnsync copy-revprops all reversions everytime executing
svnsync?
is there any document for error number?
i'm going to handler all kind of errors.
--
.
Vanity...My favourite sin.
--<>
here is my config in dav_svn.conf:
DAV svn
thank you very much, i will have a loot at this.
--
.
Vanity...My favourite sin.
--<>
-- --
??: "Johan Corveleyn";;
: 2018??1??4??(??) ????4:56
??: "Keva-Slient"<35
there are many transactions files after committing failed in my svn server.
they cost lots of inodes.
when and how can i delete them?
i've found out that server will generate new transaction dir
xx/db/transactions/[0-9]+\-[0-9]+.txn dir after each failed committing.
any tool can delete them
thank you very much. that's what i want
--
.
Vanity...My favourite sin.
--<>
-- Original --
From: "Nathan Hartman";;
Date: Wed, Jan 3, 2018 11:08 AM
To: "users";
Cc: "Keva-Slient"
thank you very much. that's exact what i want.
--
.
Vanity...My favourite sin.
--<>
-- --
??: "Nico Kadel-Garcia";;
: 2018??1??3??(??) ????11:20
??: "Keva-Slient"&
inodes usage of my svn server grows up quickly as repositories commits
increasing.
there are many reversion files in xx/db/revs/[0-9]+/[0-9]+.
is there any way storing all version files into one file? or any other way to
solve this problem.
--
.
Vanity...My favour
we use svn managing our config files.
we lock config file when do committing or writing operation.
in client side, only commit operation executes. and svndump in server.
our process is always opening file like repo/someconfig/files . it's strang
process opened tmp file like repo/.svn/tmp/svn-X
we use svn managing our config files.
in client side environment, check out repos in client side, processes could
open the config file and read or write the config file. some of them could keep
file handler for a long time.
now we get some problems: the config file will be moved to .svn/tmp
10 matches
Mail list logo