Timeline for Solving Problems using ServerFault
Current License: CC BY-SA 2.5
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:14 | history | edited | CommunityBot |
replaced http://serverfault.com/ with https://serverfault.com/
|
|
| Jul 22, 2010 at 18:07 | history | migrated | from meta.stackexchange.com (revisions) | ||
| Aug 20, 2009 at 3:34 | comment | added | rwired | Squillman, thanks for analyzing all my questions!!! You were right about the shutdown script post - I accepted the answer just because I was being nagged to! When I posted those earlier questions I don't think SuperUser was running, so thanks for moving them to the right place. | |
| Aug 19, 2009 at 5:41 | comment | added | mrdenny | The back and forth discussion is generally how server and system problems usually get fixed. From this point of view, programmers have a much easier time of things, as they have code samples to deal with. Systems folks don't always have that option as we usually don't have access to the code of the problem we are trying to fix so we have to work around the software we are dealing with. | |
| Aug 19, 2009 at 5:14 | history | answered | squillman | CC BY-SA 2.5 |