Configure sys-block/zram-init so that there is one service per mount point or swap configuration, in a similar manner that net-misc/tigervnc does per display. This would enable: 1. starting and stopping each config separately. 2. Configuring separate writeback daemons for each config. I have attempted doing this myself and it appeared to work in terms of starting stopping the services including writeback daemons. However, there were issues: My re-coding of the zram-init init script did not conform to openrc requirements. My attempts at writeback daemons were unsatisfactory in terms of: 1. Choosing when writeback was required. 2. Suspicions of memory leak when left running continuously for 2 weeks or more. Reproducible: Always Steps to Reproduce: This is an enhancement request.
I think this might be something to send upstream to https://github.com/vaeth/zram-init/?
(In reply to Sam James from comment #1) > I think this might be something to send upstream to > https://github.com/vaeth/zram-init/? Therefore, should this bug be marked as resolved?
