ChanServ changed the topic of ##yamahasynths to: Channel dedicated to questions and discussion of Yamaha FM Synthesizer internals and corresponding REing. Discussion of synthesis methods similar to the Yamaha line of chips, Sound Blasters + clones, PCM chips like RF5C68, and CD theory of operation are also on-topic. Channel logs: https://freenode.irclog.whitequark.org/~h~yamahasynths
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ej5 has quit [Read error: Connection reset by peer]
andlabs has joined ##yamahasynths
andlabs has quit [Ping timeout: 268 seconds]
andlabs has joined ##yamahasynths
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
andlabs has joined ##yamahasynths
cr1901_modern has quit [Read error: Connection reset by peer]
cr1901_modern has joined ##yamahasynths
andlabs has quit [Read error: Connection reset by peer]
andlabs has joined ##yamahasynths
andlabs has quit [Read error: Connection reset by peer]
andlabs has joined ##yamahasynths
andlabs has quit [Read error: Connection reset by peer]
andlabs has joined ##yamahasynths
_whitelogger has joined ##yamahasynths
<cr1901_modern>
whitequark: Do you run any particular script or code snippet to reconnect _whitelogger when it dies? I've noticed that it always reconnects at 46 or 47 seconds after the minute
<Sarayan>
smells like a cron
<cr1901_modern>
ahh good point
andlabs has quit [Read error: Connection reset by peer]
andlabs has joined ##yamahasynths
<emily>
disclaimer: you should not use cron to restart and manage the lifetime of important tasks, use a proper service supervisor like systemd or supervisord or runit/s6 instead
<whitequark>
emily: what i use cron for is checking if there are in fact any messages in the last X minutes
<whitequark>
and if not, i force restart the logger
<whitequark>
it's a watchdog essentially
<KitsuWhooa>
That sounds a bit unnecessary, to be honest
<KitsuWhooa>
I guess it checks for messages in every room, so having silence in all of them for log periods of time is not that common
<KitsuWhooa>
*long
<whitequark>
you don't actually have any idea what is it to run an irc logger reliably for years, do you?
<whitequark>
networks break constantly. irc makes sure to rely on as many links as possible so you get even more opportunity for strange breakage. i get something between 1 and a dozen watchdog restarts per day, and in almost a decade, i had to log in and fix it manually about three times, all of which were caused by freenode antispam k-lining me because of a false positive
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
andlabs has joined ##yamahasynths
andlabs has quit [Ping timeout: 265 seconds]
andlabs has joined ##yamahasynths
<balrog>
whitequark: are you having the logger use PING/PONG?
<balrog>
or just checking for messages
<balrog>
(I mean, if you're writing an IRC client of any sort it has to respond with PONGs, so your watchdog can trigger on lack of a PING from the server)
ej5 has joined ##yamahasynths
<emily>
not all servers reliably ping
<emily>
the best thing to do is ping if you haven't heard anything from the server in a while, and reconnect if you go N time without a pong