Sponsored Content
The Lounge What is on Your Mind? They won't need so many sys admins anymore Post 302957418 by Riker1204 on Saturday 10th of October 2015 01:34:56 PM
Old 10-10-2015
Sorry to hear this sparcguy. Hope you will keep us updated on anything you find. Always like to know how these things turn out.
 

9 More Discussions You Might Find Interesting

1. Solaris

Any sys admins from uk?

Hello Guys, im new to this forum. Im from UK and ive recently completed my SCSA I & II and also got trained in Veritas Suite (Veritas Volume Manager and Veritas Clusters, Veritas NetBackup), SAN Configuration. I was trying to get a break as a junior sun solaris admin. I am applying for the jobs... (1 Reply)
Discussion started by: megadeth
1 Replies

2. UNIX for Dummies Questions & Answers

Can't login as SU anymore - SU: NO SHELL

the root shell has been changed in the file /etc/passwd, basically pointing to an incorrect directory. So now every time we login as 'su' I get the message 'su: no shell' so we can't login as superuser. Is there an easy way to rectify this? please use step by step instructions/commands - I... (4 Replies)
Discussion started by: homechoice
4 Replies

3. AIX

won't mount /usr...won't boot fully

Hello: NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Discussion started by: bbird
11 Replies

4. Solaris

Sun Fire won't boot anymore

Hi all - I have an issue with our (way old) single processor SunFire 280R, running Solaris 9.0.4. It won't boot even after multiple power cycles. There was a power outage last week end in the computer room, so this might have to do. In normal boot mode, the screen shows a single line : ... (5 Replies)
Discussion started by: bostella
5 Replies

5. UNIX for Dummies Questions & Answers

Can't SSH as root anymore!

I've screwed something up in my sshd_config apparently, because I can't ssh with root anymore. I had disabled root login for security reasons, but then my ssh credentials with full administrative privelges stopped working. So then I reenabled root login (and reset ssh), but root now isn't... (3 Replies)
Discussion started by: cquarry
3 Replies

6. UNIX for Advanced & Expert Users

pkill won't work on firefox anymore

Can someone tell me why pkill won't work on firefox anymore? (11 Replies)
Discussion started by: cokedude
11 Replies

7. Slackware

Anyone Using Slackware Anymore?

We used to use Slackware, but then moved all our servers to Ubuntu Linux. Does anyone use Slackware anymore? (8 Replies)
Discussion started by: Neo
8 Replies

8. Programming

Interactive Python 3.5+ sys.stdout.write() AND sys.stderr.write() bug?

(Apologies for any typos.) OSX 10.12.3 AND Windows 10. This is for the serious Python experts on at least 3.5.x and above... In script format sys.stdout.write() AND sys.stderr.write() seems to work correctly. Have I found a serious bug in the interactive sys.stdout.write() AND... (2 Replies)
Discussion started by: wisecracker
2 Replies

9. UNIX for Beginners Questions & Answers

Bash script won't run because hardware won't produce display

Can anyone offer any advice on how to modify the script below to work on a new system we have, that has no graphics capability? We admin the system through a serial RAS device. I've tried running the below script through the RAS and through an ssh -X session. It failed with something like "GTK... (3 Replies)
Discussion started by: yelirt5
3 Replies
CTLUSER(8)						      System Manager's Manual							CTLUSER(8)

NAME
ctluser - control lusers SYNOPSIS
ctluser [ -h ] [ -m ] command [ argument... ] DESCRIPTION
Ctluser sends a message to the control channel of a given luser(8) This command can only be run by the sysadmin(1) In the normal mode of behavior, the message is sent to the luser's brain, which then performs the requested action and sends back a reply with a text message and the exit code for ctluser. If the luser's brain successfully performed the command, ctluser will exit with a sta- tus of zero and print the reply on standard output. The ``-m'' flag is used to display an MPEG of the results of the given command on the console of the sysadmin(1) Note that this requires the sysadmin(1) to be running an X server. To see a command summary, use the ``-h'' flag. If a command is included when ctluser is invoked with the ``-h'' flag, then only the usage for that command will be given. The complete list of commands follows. Note that all commands have a fixed number of arguments. If a parameter can be an empty string, then it is necessary to specify it as two adjacent quotes, like "". addhist <entry> Add an entry to the luser's employment record. allow reason Allow a luser to use the computer system again. The reason must be the same text given with an earlier ``reject'' command. Note that this command is currently not implemented. begin name Begin a new luser(1) with the given file. Note that this command is currently not implemented. cancel pid Causes a process of a luser to be killed changegroup group Changes a luser from their current workgroup to the one specified. checkfile Forces a user to return to a paper based system drop Causes a large mass to drop onto the luser from a great height. flushlogs Destorys all logs of the actions done by the sysadmin(1) to the luser. go reason The luser is fired for the given reason. hangup Makes the luser hang themselves mode Displays the operating mode of the luser newgroup group Causes a luser to make their own newgroup up pause thought Makes the luser pause for the given thought. Note that this may cause some lusers to crash shutdown reason Makes the luser shutdown. This is essentially the same as killing them signal sig Sends the given signal to the luser throttle reason Causes the luser to throttle themselves trace item flag Gives the sysadmin(1) information on what the luser is doing. BUGS
Ctluser sometimes has the effect of lusers complaining the to management. The use of bosskill(8) maybe required at this point. HISTORY
Written by Simon Burr <simes@tcp.co.uk>. Based upon the manual page for ctlinnd(8), part of the InterNetNews system. SEE ALSO
luser(1), sysadmin(1), bosskill(8) 19 October 1995 CTLUSER(8)
All times are GMT -4. The time now is 07:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy