[GitHub] sklassen commented on issue #27: vm.args is now editable -- enabling clusters; snap set works for name and cookie

[GitBox <gi...@apache.org>]

sklassen commented 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-435578838
 
 
   Hi @wohali,
   
   Great. Thanks for all your help in guiding me through. 
   
   I played around with the apt-get method. I thought it was as easy as moving /opt/couchdb to /snap/couchdb/xx and modifiying the snap_run script; but the snap build process is fickle and time consuming. During this process I learnt how to remove the unneeded erlang libraries. That solved the size issue. I then reasoned that if apt-get package is available, then it should be called directly. Whereas this snap build is helpful for private label packages with specific configuration, or for versions yet-to-be-packaged. 
   
   There is one other issue I'm working on regarding the compaction daemon. The log gets several warnings.
   Nov 02 00:22:01 sigyn couchdb.server[23866]: [warning] 2018-11-01T16:22:01.828489Z couchdb@127.0.0.1 <0.238.0> -------- Compaction daemon - skipping database `shards/e0000000-ffffffff/_global_changes.1540581873` compaction: the estimated necessary disk space is about 12248 bytes but the currently available disk space is 0 bytes.
   Nov 02 00:27:15 sigyn couchdb.server[23866]: [info] 2018-11-01T16:27:15.763198Z couchdb@127.0.0.1 <0.53.0> -------- alarm_handler: {set,{{disk_almost_full,"/snap/gnome-calculator/260"},[]}}
   
   snapd restricts access to mount information. I added the :mount-observe interface and explicitly gave permission to it. But I think this method only works for user-run programs, but for daemons. The CouchDB compactor should probably know not to bother with disk checks on /snap/ as is read-only system. In the meantime, for snap couchdb, the compactor should be disabled.
   
   I'll open a new branch and raise a PR. Then I think we're ready. I assume you'll publish from your end?

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services