07-23-2007
It doesn't happen at boot because it is rare that you need to populate the /dev directory and most people like a reboot to complete as quickly as possible. If you really want to run "insf -e" on every reboot you could add another script to the bootup scripts to do that.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
We use SCO OSR5 with TermLIte to create telnet sessions.
If you accidently click X on the TermLite screen and exit the session you leave process running. I've heard of a program that will allow you to re-connect to these 'floating' sessions and then be able to carry on your session.
Does anyone... (2 Replies)
Discussion started by: mikeh
2 Replies
2. Cybersecurity
On AIX 4.3.3 , how telnet access will be allowed to few users only whereas other will not be able to telnet the server? (6 Replies)
Discussion started by: amit
6 Replies
3. UNIX for Advanced & Expert Users
Anyone know how to limit the telnet sessions on a per user basis on an HP UX Box.
I would like to limit the Maximum number of telnet seesions a user can open at any give time to around 4 or 5. I have been looking and looking and do not seem to be able to find anything on this. Any help would be... (2 Replies)
Discussion started by: Witlr
2 Replies
4. Solaris
I am trying to find the following information regarding the logging of telnet sessions within a Solaris 10 environment:
(1) How can I tell if the logging of telnet sessions is enabled on a Solaris 10 machine?
(2) Assuming that the logging of telnet sessions is not enabled, what is the... (1 Reply)
Discussion started by: RobSand
1 Replies
5. Red Hat
Hi Users,
Kindly help me with below query of mine.
Using Red Hat Linux Enterprise Edition as the client how many simultaneous
1) Maximum FTP sessions are allowed
2) Maximum Telnet sessions are allowed
3) any special settings need to be enabled for maximum telnet and ftp sessions on... (2 Replies)
Discussion started by: newbie07
2 Replies
6. UNIX for Advanced & Expert Users
Hi Users,
Kindly help me with below query of mine.
Using Red Hat Linux Enterprise Edition as the client how many simultaneous
1) Maximum FTP sessions are allowed
2) Maximum Telnet sessions are allowed
3) any special settings need to be enabled for maximum telnet and ftp sessions on... (2 Replies)
Discussion started by: newbie07
2 Replies
7. HP-UX
Currenly my hp-ux server can take the default of 60 telnet connections,
i want to know how i can increase this. and also can i effect such changes without doing a reboot.
My server is HP-UX B.11.23 (1 Reply)
Discussion started by: tomjones
1 Replies
8. Solaris
hello guys, Does anybody know how I can log all the telnet sessions for a specific IP.
For instance, anybody who make a telnet to IP x.x.x.x this session will be logged. the purpose of it is that I need to know every command that people are running on this node.
Any help ?
Thanks. (1 Reply)
Discussion started by: cerioni
1 Replies
9. Solaris
Hi,
My requirement - for security purpose -
I want all root logins to my solaris servers are done by a script kept
in a separate unix box. This script will telnet into remote solaris server with
root user and log every session via log file.
Now my purpose is to log every telnet session... (3 Replies)
Discussion started by: rahul_jain250
3 Replies
10. AIX
Hi
The telnet sessions stay as idle users. It is not getting kicked out.
Please advise what could be the issue. only when we reboot the server these telnet sessions goes.
Below is the current output from the server. we rebooted the server three days ago:
pmut6:/> uptime
04:21PM... (8 Replies)
Discussion started by: newtoaixos
8 Replies
REBOOT(8) BSD System Manager's Manual REBOOT(8)
NAME
reboot, halt, fastboot, fasthalt -- stopping and restarting the system
SYNOPSIS
halt [-lnpq] [-k kernel]
reboot [-dlnpq] [-k kernel]
fasthalt [-lnpq] [-k kernel]
fastboot [-dlnpq] [-k kernel]
DESCRIPTION
The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and,
respectively, halt or restart the system. The action is logged, including entering a shutdown record into the user accounting database.
The options are as follows:
-d The system is requested to create a crash dump. This option is supported only when rebooting, and it has no effect unless a dump
device has previously been specified with dumpon(8).
-k kernel
Boot the specified kernel on the next system boot. If the kernel boots successfully, the default kernel will be booted on successive
boots, this is a one-shot option. If the boot fails, the system will continue attempting to boot kernel until the boot process is
interrupted and a valid kernel booted. This may change in the future.
-l The halt or reboot is not logged to the system log. This option is intended for applications such as shutdown(8), that call reboot
or halt and log this themselves.
-n The file system cache is not flushed. This option should probably not be used.
-p The system will turn off the power if it can. If the power down action fails, the system will halt or reboot normally, depending on
whether halt or reboot was called.
-q The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n
option is not specified). This option should probably not be used.
The fasthalt and fastboot utilities are nothing more than aliases for the halt and reboot utilities.
Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending
doom and cleanly terminating specific programs.
SEE ALSO
getutxent(3), boot(8), dumpon(8), nextboot(8), savecore(8), shutdown(8), sync(8)
HISTORY
A reboot utility appeared in Version 6 AT&T UNIX.
BSD
October 11, 2010 BSD