- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Determine single-user run-level
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2004 07:02 AM
04-28-2004 07:02 AM
. run-level 3 Apr 26 13:54 3 0 S
which is exactly what it returned when the system was in run-level 3. (I'm assuming this is because /var/tmp/wtmp isn't available because /var isn't mounted.)
Trying to enter single-user mode with "init s" allows "who -r" to return the correct run-level, but the system is still running all processes it was in run-level 3 so the script would fail anyway since there are open files in the file system still.
Ideas?
Jeff Traigle
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2004 07:05 AM
04-28-2004 07:05 AM
Re: Determine single-user run-level
who -r should correctly tell you.
init 1
might do the trick. If you can be at the console, you may see where it's stopping.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2004 07:08 AM
04-28-2004 07:08 AM
Re: Determine single-user run-level
I'm afraid you're going to have trouble doing it this way for the reasons you're already seeing - not everything will be stopped.
You really have to reboot the system & stop the autoboot at the BCH> bo pri then Y to interacct w/ISL? ISL>hpux -is
That's the only sure way to do this.
Rgds,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2004 07:20 AM
04-28-2004 07:20 AM
SolutionCreate an rc script that extends the lvol in /etc/rc1.d/SNNscript_name. and reboot the server. Just make sure all commands needed are available at the time ( NN number) the script is run, and make sure you do not have a typo.
HTH,
Gideon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2004 07:36 AM
04-28-2004 07:36 AM
Re: Determine single-user run-level
Jeff Traigle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2004 07:50 AM
04-28-2004 07:50 AM
Re: Determine single-user run-level
Just make sure you remove/disable the script after completion.
Gideon
( 0 Points please)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2004 08:05 AM
04-28-2004 08:05 AM
Re: Determine single-user run-level
What FS are you extending?
/ , /stand , primary swap are definite NO GOs.
No matter what you do because they *have* to stay contigous. Ignite tapes are the only way to do these.
/usr , /var , /opt & probably even /tmp will be problematic but might be possible.
But it seems to me to be running a big risk for what? A couple of extra minutes. You *still* have to stop everything. If you mess up an FS because of an unseen event or parameter you'll spend *much* more time recovering than you would have used going all the way to reboot.
Your call,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2004 08:28 AM
04-28-2004 08:28 AM
Re: Determine single-user run-level
Jeff Traigle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2004 08:41 AM
04-28-2004 08:41 AM
Re: Determine single-user run-level
Just make sure that /etc/default/security contains NOLOGIN=1 . Then just touch /etc/nologin or better yet put some text in it like "System login prohibited at this time - maintenance in progress."
Then you can boot users off (fuser?), stop the app & umount the FS & extend it. Then just undo all this & voila - mission accomplished.
One caveat - make sure root's home dir is *not* in the same VG as the regular users if $HOME is involved here - use /root or something.
If vg00 is out of the picture - things are much, much easier.
My 2 cents,
Jeff