network profile
| bio | website | joeshaw.org |
|---|---|---|
| location | Cambridge, MA | |
| age | 33 | |
| visits | member for | 2 years, 2 months |
| seen | Nov 16 '12 at 21:00 | |
| stats | profile views | 0 |
Open source programmer, mainly in C, Python, JavaScript, and C#.
|
Nov 16 |
comment |
Why might a 413 not be flushed to the client immediately? Yeah, this will likely result in the client reporting "connection reset by peer" rather than actually reading and parsing the response body. |
|
Mar 1 |
comment |
Can monit be configured to never unmonitor/timeout a service? This is exactly what I ended up doing, but I'm not too happy about it. |
|
Jan 10 |
awarded | Announcer |
|
Nov 7 |
awarded | Student |
|
Sep 23 |
comment |
Can monit be configured to never unmonitor/timeout a service? Looking at the monit page for the service, existence field is set to that. But the rule just doesn't seem to be obeyed. With a service that is designed to fail (ie, just a shell script that echoes out the date and does exit 1) it still unmonitors quickly. If I use "monit monitor joe-test" it stops monitoring after one failure. With "monit start joe-test" it gives up after 2 tries. |
|
Sep 20 |
comment |
Can monit be configured to never unmonitor/timeout a service? gist.github.com/1229828 -- I removed some mail server/alert stuff and the HTTP server configuration from monitrc. The other file is an example of our service configuration. Note the lack of "if x restarts then timeout" clause in it. |
|
Sep 20 |
asked | Can monit be configured to never unmonitor/timeout a service? |
|
Jun 29 |
awarded | Supporter |
|
Mar 13 |
awarded | Autobiographer |
