« first day (2453 days earlier)      last day (152 days later) » 

5:54 PM
Haven't read all the conversation, but I like the fact that it's about git/SC integration! Anything that makes it easier is good in my book.
 
6:16 PM
in The 2nd Monitor, 18 secs ago, by Simon Forsberg
Duga has been down for a few days because someone forgot to start her after a reboot
 
@SimonForsberg just to clarify - does that mean Duga is back in service? does the hook need ot be updated?
 
No hook changes needed, she should be back now
 
@SimonForsberg is there no autoexec.bat command to start Duga?
 
@HackSlash autoexec.bat, lol, that was a long time ago
No sadly she's not being autostarted
If anyone would like to create a monitoring tool to check if she's alive, feel free to do so :)
I could really use some monitoring tool for plenty of stuff
 
What is the server upon which Duga runs? (I know nothing about Duga)
(It's obviously not a DOS server because that doesn't exist)
 
6:22 PM
Her old code is running on Tomcat, a Java servlet container. Some work is ongoing to migrate her to run within a Java application in a simple Docker container
The physical machine is in my kitchen
 
Oh! So you could install Duga as a service that runs on start. I was asking about the OS because the way you do that is different on each one but we could get it done if you want.
 
@HackSlash Ah, the OS is Ubuntu
 
6:44 PM
Great! So you should have many options to start things at boot: askubuntu.com/questions/228304/…
Looks like systemd is the modern way to make your program into a "service"
A unit configuration file whose name ends in .service encodes information about a process controlled and supervised by systemd. This man page lists the configuration options specific to this unit type. See systemd.unit(5) for the common options of all unit configuration files. The common configuration items are configured in the generic "[Unit]" and "[Install]" sections. The service specific configuration options are configured in the "[Service]" section. Additional options are listed in systemd.exec(5), which define the execution environment the commands are executed in, and in systemd.kill(5), which define the way the processes of the service are terminated, and in systemd.resource-control(5), which configure resource control settings for the processes of the service. If a service is requested under a certain name but no unit configuration file is found, systemd looks for a SysV init script by the same
 
@SimonForsberg Keep it in the sink for water cooling!
 
systemd can run it at boot and rerun it if it crashes. While external monitoring is nice to show users the status of your service, local monitoring should keep it going for you so you don't have to manually touch things anymore.
If you had something like this:

[Service]
Restart=always
RestartSec=30

It would only be down for 30 seconds before being auto-started again.
 
@FreeMan I'm no expert but I was told that water and electric doesn't mix very well.
 
7:00 PM
@this LTT would disagree with you: youtube.com/watch?v=CFXyyJyEtVI
 
@this Depends on what you're expecting from the mix.
 
 
8:03 PM
@FreeMan Excellent tip, thanks
 
8:26 PM
@FreeMan I figured water cooling systems were more of a compensation thing.
 
9:03 PM
Today's route. Going down a Skiwi-sized-tab-count-reading-bonanza on docs and suggestions.
 

« first day (2453 days earlier)      last day (152 days later) »