I’m not the techy person behind our pool so I can give you the command line but I don’t know much else after that.
cd ~/git
./leaderLogs.py --pool-id pool id here --epoch 240 --vrf-skey $CNODE_HOME/priv/pool/TBO/vrf.skey -bft --sigma 0.0008755706338504188
If you put another pools ID it still shows your own slot allocation.
Yeah a pool could easily shut down for an epoch, turn on just before the snapshot to see if they have block allocation, if not then close down again. It wouldn’t do any harm at all.
However, you have to be sure the nodes and relays will start up without any issues each time. Also if you are running your pool off a cloud based server then you’re not achieving anything by turning it all off. Maybe people running hardware servers in their own homes or something, but the power consumption is so low, not sure it would really have any benefits.
I would say turning nodes and relays off when there is no block allocation is just unnecessary people hours with the small risk of problems when starting up again.