Talk:System administrator

message: Pazhaniyappan has been nominated to be improved by Wikipedia:This week's improvement drive. Vote for this article to support it.--Fenice 06:56, 11 August 2005 (UTC)
replies: text: Fix the mistakes and gives back the permission's to source (talk) to maneged his own content 147.236.230.235 (talk) 15:15, 5 March 2024 (UTC)
thread_title: Improvement Drive

message: I'd like to add more descriptive text here about the actual career of being a Sys Admin. Like typical career paths, Sys Admin burnout, average age rage, typical length of time that a person stays in this career, average pay by region, and others. You get the idea. Make this article have more about the general characteristics of the role as seen by those who experience it. I'll be working on it, but I wanted to kick off some discussion about it, and see what other's ideas might bring up to include along these lines. --NightMonkey 08:45, 5 October 2005 (UTC)
replies: text: I would expect the SAGE annual survey would be an excellent source of reliable data for this.  Do you have access to them?  — Coren (talk) 01:21, 13 November 2008 (UTC)
thread_title:  The SysAdmin's Career

message: I'd like to request some info that sysadmins could use. Just like we have very in-depth articles on diseases, plants and what-not. It could easily link to many of the software categories that i've found useful from time to time. -- 12:21, 5 October 2006 (UTC)
thread_title:  Resources 

message: I re-removed the comments:
"However, some employers consider reliance on such certifications to be a sign of a poor candidate, one with trade-school "book learning" rather than formal theoretical knowledge or hard practical experience."
The statement in that paragraph is that 1.) employers often require experience. 2.) sometimes they expect certifications.  Maybe some people think that certifications are just "book learning", but that's besides the point.  We're talking about what kind of training a job as a sysadmin might require, and sometimes you just have to get a cert.  Maybe someone could add something a bit more neutral about certifications vs. experience?  (BTW, I have no certifications yet am a sysadmin). -- JSBillings 13:17, 29 August 2007 (UTC)
replies: text: Well, it would be original research to cite it, of course, but I've spoken with a number of senior sysadmins (in a position to hire others) who think rather negatively of resumés that present certifications as a proof of competence. --FOo 01:29, 30 August 2007 (UTC)
thread_title:  re-removed negative comments about certifications 

message: It's interesting that software developer is not mentioned in the list of related fields, especially since the article itself says that SA's do some programming. Moreover, the article also emphasizes that SA's are not software developers or computer programmers. Well, if the relationship is that close, that the two roles could be confused and need explicit differentiation in the article, doesn't that imply that they are also close enough for software developer to be listed under "Related Fields"? Toddcs (talk) 14:14, 29 November 2010 (UTC)
thread_title:  Related Fields 

message: I and many other computer owners have had a message asking for a system administrator when no human system administrator exists. This article does not address what segment of the computer program is being asked for when the computer asks for a system administrator's permission and no system administrator or path to a system administrator exists.Richard Dates (talk) 05:23, 17 August 2008 (UTC)
thread_title:  Inadequate definition 

message: I don't think a merge is appropriate.  This article discusses the position, whereas superuser discusses a technical feature of some OS for privileged operations.  — Coren (talk) 01:19, 13 November 2008 (UTC)
replies: text: I concur, no merge, please. Many operating systems just don't have the concept of "SuperUser". Palm OS, DOS, Embedded Systems,etc. Being able to login as a superuser is just one of many tools and privileges often associated with the work of a SysAdmin, like having console access or having the keys to the data center cage. It is theoretically possible to be a SysAdmin and never have "superuser" access, as the systems maintained could actually not have the concept implemented therein. Keep the articles seperate. --NightMonkey (talk) 23:30, 13 November 2008 (UTC)
thread_title:  Merge? 

message: Hey, y'all. I'm just giving a heads-up here: please don't add any more unsourced content to the article. I threw on the sources tag specifically to get more sourced text (most of the article is not sourced). Adding more unsourced material (especially material that isn't very encyclopedic) will just result in its removal. Thanks. --NightMonkey (talk) 21:17, 10 December 2008 (UTC)
thread_title:  Sourcing 

message: Article may be subjected to vandalism. See the following xkcd-comic http://xkcd.com/705/  —Preceding unsigned comment added by 81.166.157.168 (talk) 11:35, 23 February 2010 (UTC)
thread_title:  Suggestion for semi-protection 

message: There may be a bit too much commentary on personal experience of the job here:  
I.e.:  "However, perhaps the most important skill for a system administrator is problem solving -- frequently under various sorts of constraints and stress... "
It's fair enough to mention that a Sys Admin may work under tight timelines, then again, is that more true of this job than any other such that it needs to be pointed out?  Stress is a human experience to time pressures, and not one that everyone experiences, so this is out of place in a factual description (unless you want to note that Sys Admins often report a high stress level, per some study).  —Preceding unsigned comment added by 68.146.192.74 (talk) 19:13, 13 September 2010 (UTC)
replies: text: I have been system administrator for some years already and I do not think fixing stuff is the most important skill. The whole profession is about serving people in their computing needs, because they do not have time, knowledge, interest etc 'insert here reason' to do it themselves. The service is supposed to be discreet, but often when things go bad enough wrong clients get interested what system administrators do. While some system administrators feel client interest stressful the true professionals aim to get on top that situation, which means communicating with clients. IMHO the most important skill in system administration is to understand the role is about making systems to behave the way clients want and need. At the times of crisis, when people are in panic keeping calm and carrying on is also useful skill to posses, thought not absolutely necessary. If one does better job in mental state of panic that is also fine. No-one cares the style when clients are happy. Sami Kerola (talk) 11:37, 23 January 2012 (UTC)
thread_title:  Personal commentary 

message: The New Oxford American Dictionary defines "system" as "a set of connected things or parts forming a complex whole", and the professional organization SAGE (System Administrator's Guild, a USENIX SIG: http://www.sage.org/field/field.html) uses the mass noun form, therefore I propose that the proper term for use in this article is "system administrator". 
Doctorgage (talk) 14:18, 20 December 2010 (UTC)
thread_title:  "system administrator" vs "systems administrator" 

message: Bleh, this needs a rewrite. The last paragraph under the heading "Duties of a system administrator" lists three related fields: "System administrators, in larger organizations, tend not to be system architects, system engineers, or system designers.". The first links to an article that describes computer system architect; while the latter links to an article that includes mention of computer system design. However, the article at Systems engineering does not adequately describe computer systems engineering. I would actually suggest that these related fields are moved to the "Related fields" section, and each field summarized and broken out into a new article that more fully describes each skill. There's also mention of the lines of demarcation being less well defined in smaller organizations -- that could simply refer to the "Related fields" rather attempt to define a whole 'nother set of related fields. Just my two pennorth.--Rfsmit (talk) 20:43, 15 February 2011 (UTC)
thread_title:  No such article on (operating) systems engineering 

message: and a picture of your typical system administrator at work.  —Preceding unsigned comment added by 109.171.137.211 (talk) 11:52, 20 May 2011 (UTC)
thread_title:  Needs more [[LART]] 

message: A lot of the external links listed are really crappy sites that don't add anything whatsoever. isystemadmin.com? Really? 
I propose removing the link to http://www.isystemadmin.com/, http://linux-administration-pro.com/, http://www.administration-systeme.com/, http://www.artduweb.com/, and BigAdmin (since the Sun acquisition by Oracle, it just gets redirected to the Sun homepage). 
Thoughts? 
StandaloneSA (talk) 10:33, 20 June 2013 (UTC)
thread_title:  Crappy External Links 

message: Per the Wikipedia:Good article criteria: 
:Illustrated, if possible, by images:[8]
:images are tagged with their copyright status, and valid fair use rationales are provided for non-free content; and
:images are relevant to the topic, and have suitable captions.[9]
:
I am adding back in the original image, from June 2013. If you have a valid reason to remove it, discuss it here, otherwise leave it alone. 
StandaloneSA (talk) 00:43, 29 December 2013 (UTC)
thread_title:  Removal of photograph of professional system administrator 

message: I can't get Matplotlib to work in python. I tried to install the programs but they all said "no modules names (numpy, setup, etc)". What do I have to do to make it work??  — Preceding unsigned comment added by 71.232.176.64 (talk) 00:14, 28 September 2014 (UTC)
thread_title:  Can't get Matplotlib to work in Python 

message: gfulyfiojo[ihczxiucgcl'iccodsi.sydc
Hello fellow Wikipedians,
I have just added archive links to  on System administrator. Please take a moment to review my edit. If necessary, add  after the link to keep me from modifying it. Alternatively, you can add  to keep me off the page altogether. I made the following changes:
*Added archive https://web.archive.org/20150402103548/http://nssa.rit.edu/~nssa/?q=node/8 to http://nssa.rit.edu/~nssa/?q=node/8
When you have finished reviewing my changes, please set the checked parameter below to true to let others know.
Cheers. —cyberbot IITalk to my owner:Online 02:19, 30 August 2015 (UTC)
thread_title:  External links modified 

message: The source for sources 7 and 8 are no longer active, they link to a 404 page  — Preceding unsigned comment added by 165.139.179.197 (talk) 15:41, 6 December 2016 (UTC)
thread_title:  Sources no longer active 

message: Don't have time to use this tonight, but one of the images from here might be nice to use to illustrate the training section - they show faces and computers more clearly than the current image. —Luis (talk) 04:42, 14 May 2018 (UTC)
thread_title:  Possible image for training section 

message: Strongly train and organize good and effective administrators to meet the goals and objectives of the Wikimedia Foundation. (Non-profit organization)
https://th.wikipedia.org/wiki/วิกิพีเดีย:ผู้ดูแลระบบ?action=edit#รายการผู้ดูแลระบบ
  — Preceding unsigned comment added by Longlivethekingofthailand (talk • contribs) 17:22, 29 July 2018 (UTC)
thread_title:  https://th.wikipedia.org/wiki/วิกิพีเดีย:ผู้ดูแลระบบ?action=edit#รายการผู้ดูแลระบบ 

message: can you unlock my cb  — Preceding unsigned comment added by 2601:408:C302:5970:78F5:83F:DEA1:9698 (talk) 19:42, 24 April 2020 (UTC)
thread_title:  can you unlock my cb 

message: SRE is a google branded term for DevOps which is a modern take on system administration that seeks to differentiate itself from tradition SysAdmin responsibilities.
An equivalent analog is Facebook's "Production Engineer" position and the more generally applicable DevOps would be more appropriate but I recommend the exclusion of these terms entirely. They exist to distinguish a role which intends to not be system administration. 
I recommend either removing mentions of SRE or including both Production Engineer and Devops, with the intent of including any other terms that may be generated in the future.  — Preceding unsigned comment added by 24.143.116.46 (talk) 05:29, 23 April 2021 (UTC)
thread_title:  Remove SRE or include Devops and Production Engineering 

message: how to put out password 41.115.50.182 (talk) 15:23, 8 June 2021 (UTC)
replies: text: Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format and provide a reliable source if appropriate. ScottishFinnishRadish (talk) 15:30, 8 June 2021 (UTC)
thread_title:  Semi-protected edit request on 8 June 2021 

message: It is not ok 2603:9001:490A:1CDA:C2F8:B930:B376:5E17 (talk) 23:22, 13 March 2022 (UTC)
thread_title:  Endne