Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cancel user login

Status
Not open for further replies.

Diamon

Technical User
Jul 18, 2002
19
DE
Hi all,

i've heard of a file that, as long as it's exists, prevents new user to login. Is that correct and if yes, how it's name?

Thx in advance...

Diamon
 
Hi

Yes you are correct.creat a file called /etc/nologin
and this is going to prevent new users from entering the system.

a_k_vishwakarma@yahoo.co.in
 
Not sure of your definition of 'new' here, but /etc/nologin will stop any user (except root) from logging in whilst it exists.
 
hmm, I checked it out and root is still able to login but other user don't...
 
And was that what you wanted? Bear in mind that root must be able to login in order to remove the /etc/nologin file when users are to be allowed in again!
 
Yes, just what i wanted. Root is the only user who can login at that time, so there's no risk to lock myself out. I want it to prevent user login while i update a node to a new ML etc.

Diamon
 
I would boot into "maintenance mode" There are certain things running that may prevent you from upgrading the ML...

I would seriously consider NOT using nologin for ML upgrades...
 
Hi,

I have a suggestion that may work. You could
stop your tcpip subsystem and this way no can log onto
your box. You will have to perform any maintenace
via the control workstation, terminal, hooked up directly
to your host.

Here are the results by entering in the stop/startsrc commands:


# stopsrc -g tcpip
0513-044 The snmpd Su
0513-044 The muxatmd
0513-044 The tftpd Su
0513-044 The /usr/sbi
0513-044 The /usr/sbi

Result of trying to login in:

C:\>telnet 128.55.66.88
Connecting To 128.55.66.88...Could not open a connection to host: Connect failed

# startsrc -g tcpip
0513-059 The inetd Subsystem has been started. Subsystem PID is 23894.
0513-059 The gated Subsystem has been started. Subsystem PID is 6364.
0513-059 The named Subsystem has been started. Subsystem PID is 28028.
0513-059 The routed Subsystem has been started. Subsystem PID is 17610.
0513-059 The rwhod Subsystem has been started. Subsystem PID is 28030.
0513-059 The iptrace Subsystem has been started. Subsystem PID is 28596.
0513-059 The xntpd Subsystem has been started. Subsystem PID is 6366.
0513-059 The timed Subsystem has been started. Subsystem PID is 28598.
0513-059 The snmpd Subsystem has been started. Subsystem PID is 11614.
0513-059 The dpid2 Subsystem has been started. Subsystem PID is 11096.
0513-059 The dhcpcd Subsystem has been started. Subsystem PID is 10838.
0513-059 The dhcpsd Subsystem has been started. Subsystem PID is 10090.
0513-059 The dhcprd Subsystem has been started. Subsystem PID is 10840.
0513-059 The ndpd-host Subsystem has been started. Subsystem PID is 8050.
0513-059 The ndpd-router Subsystem has been started. Subsystem PID is 100
0513-059 The tftpd Subsystem has been started. Subsystem PID is 10842.
0513-059 The mrouted Subsystem has been started. Subsystem PID is 19252.
0513-059 The pxed Subsystem has been started. Subsystem PID is 21072.
0513-059 The binld Subsystem has been started. Subsystem PID is 30138.
0513-059 The muxatmd Subsystem has been started. Subsystem PID is 21074.


Then, I was able to log in.

Good Luck,

-Joe
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top