sklassen edited a comment on issue #27: vm.args is now editable -- enabling 
clusters; snap set works for name and cookie 
URL: https://github.com/apache/couchdb-pkg/pull/27#issuecomment-417408811
 
 
   Hello @wohali, 
   
   CouchDB has been my favorite DB for many years now, and I'm excited to 
contribute back. Thanks for your guidance. 
   
   Two new commits: configure now support for adding/modifying local.d/*.ini 
files from the command line; I also pushed the snap.ini specific ini file back 
within the standard local.d couchdb convention; and, for sanity, I've switch 
logging back to default stderr, which is cleaner and faster.
   
   And I moved my Readme.md changes into the snap directory. I'll leave the 
root Readme.md unchanged, or you can change it to reflect what you feel best.
    
   I have been reading through the travis.yml file. I'm still not sure where to 
start. Perhaps you can add a travis.yml file here first. All my changes are 
with the snap directory and snapcraft executes cleanly.
   
   As a heads up, snap installations have a similar issue to couchdb#1097 
"CouchDB 2.1.1: Compaction daemon - unable to calculate free space for 
`/run/user/0`: `enoent`" In the case with snaps the common directory is mounted 
with a zero space. I think the solution is for there to be a variable in the 
compaction daemon configutation that allows you to override the file system it 
uses for monitoring. 
   
   The exact error is this:
   
   -------- Compaction daemon - skipping database 
`shards/40000000-5fffffff/_global_changes.1533989923` compaction: the estimated 
necessary disk space is about 12852 bytes but the currently available disk 
space is 0 bytes.
   
   Should I reopen #1097 or do you want a new ticket?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to