mopfel-winrux

I'm trying to do the same. I'm able to login but when I set the management proxy keys I get the following:  

I'm experiencing the same issue with iwtf group

I was able to replicate the issue using v2.7 on Digital Ocean running 14 comets with 4GB of ram and 20GB of swap. Switching over to this PR I tried...

If I run it without `--loom 32` I get the following: ``` $ ./urbit chop zod/ loom: mapped 2048MB boot: protected loom live: loaded: MB/277.282.816 boot: installed 652 jets loom:...

I ran `trace -fp [$PID] -Trfe trace=read,lseek 2> system.trace` with all the urbits running and got the below trace https://nyc3.digitaloceanspaces.com/mopfel-winrux-s3/mopfel-winrux/2023.6.01..12.58.45-system.trace

@mrdomino I'm sorry I completely missed this. We should also do this for `lick.c`

It makes multiple sockets. One per `[%spin name=path]` card it is given. It puts them in `.urb/dev/ folder under the name path. we could use that directory

I ran the `make test` and below are my results [liblmdb_test.txt](https://github.com/urbit/vere/files/10807304/liblmdb_test.txt)

I tired this on our ARM build server and was able to properly chop. I also got the following stacktrace from the coredump on my raspberry pi 4B+ 8GB ```...

Vere writes a snapshot every 2 minutes which is probably what youre seeing. There is a flag `--snap-time` you can use to set the snapshotting rate in minutes.