| bio | website | evancoleman.net |
|---|---|---|
| location | New York, NY | |
| age | 22 | |
| visits | member for | 2 years, 1 month |
| seen | May 17 at 15:17 | |
| stats | profile views | 8 |
|
May 10 |
awarded | Popular Question |
|
Apr 5 |
comment |
Running Node.js at boot Thanks! It seems to be working. |
|
Apr 5 |
accepted | Running Node.js at boot |
|
Apr 4 |
asked | Running Node.js at boot |
|
Feb 5 |
comment |
See requests to real server with mod_proxy This seems like it would be the simplest way to do it. Thanks for the help! |
|
Feb 5 |
accepted | See requests to real server with mod_proxy |
|
Feb 2 |
asked | See requests to real server with mod_proxy |
|
Nov 12 |
comment |
Caching API Proxy Server @devicenull I'm assuming it is cacheable because I was asked by the API's company to implement a caching server. I do have an API key that is part of the request URL. Also, I was referring to data usage, not transfer speed. I should have been more specific. |
|
Nov 12 |
asked | Caching API Proxy Server |
|
Jun 6 |
comment |
OpenVPN up directive not working That worked! Thanks! |
|
Jun 6 |
accepted | OpenVPN up directive not working |
|
Jun 6 |
awarded | Editor |
|
Jun 5 |
comment |
OpenVPN up directive not working Yup, same problem. I also realized I forgot to post the error. I've edited my post. |
|
Jun 5 |
revised |
OpenVPN up directive not working added 246 characters in body |
|
Jun 4 |
comment |
OpenVPN up directive not working Nothing in audit. And what do you mean by "checked selinux? |
|
Jun 4 |
comment |
OpenVPN up directive not working This is logged in messages: WARNING: Failed running command (--up/--down): external program exited with error status: 126 |
|
Jun 4 |
asked | OpenVPN up directive not working |
|
Apr 16 |
accepted | named gets killed |
|
Apr 16 |
comment |
named gets killed Great, thanks! Only time will tell if this is actually working. So far, memory usage seems to be down. |
|
Apr 16 |
awarded | Commentator |