09-27-2010
Sorry about the lack of tags. I haven't posted in a long time and didn't catch the hint.
We're in the process of closing out the applications on this server and when I'm capturing the user stats every 15 minutes I was just getting annoyed at being over by two no matter the time of day so I thought I'd clean them if it was easy to do. Not worth a reboot though. I can just keep explaining that the 2 users on at 2AM every day are not really there.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have customers on our AIX/UNIX node startup a process that becomes stranded or orphaned and must be killed. I would like to create a script to check for these orphan processes and kill them. I can have cron run this job. The customers process will run and after 24 hours time out leaving an... (4 Replies)
Discussion started by: rjohnson
4 Replies
2. Shell Programming and Scripting
Hi,
Can I kill process submitted by another uesr (say user1) if I'm not the su. If I got some previledges granted from user1, can I kill user1's process? Please advise? Thank you very much!
Regards,
Tse (4 Replies)
Discussion started by: tsesukfan
4 Replies
3. UNIX for Dummies Questions & Answers
Is there an easy way to find all stale mounts on a system? (2 Replies)
Discussion started by: derf912
2 Replies
4. UNIX for Dummies Questions & Answers
hi, i was trying to mirror root volume group and the command i was using didnt respond for a long time
mirrorvg -m rootvg hdisk1
I was checking rootvg and it gives below. how do i fix stale partitions?? it seems to be on hdisk1
LV NAME TYPE LPs PPs PVs LV STATE ... (2 Replies)
Discussion started by: karthikosu
2 Replies
5. UNIX and Linux Applications
There are a filesystem /GWD/appbase/projects/GRIDDB
Under this filesystem there is a directory called backup.
But When I am trying to access the backup directory ,it is showing me the following error:
# cd /GWD/appbase/projects/GRIDDB
# cd backup
-bash: cd: backup: Stale NFS file handle
... (3 Replies)
Discussion started by: alphasahoo
3 Replies
6. AIX
my AIX server used to have scsi disk hdisk4. Now i removed that disk. But still it is still listed in lspv. So how can i remove the stale entry of it ? (6 Replies)
Discussion started by: navadeep
6 Replies
7. Shell Programming and Scripting
Hi all,
This is my first post.
I am new to unix scripting.
My requirement is as follows :
We are using a financial backoffice application.
Now at the end of day we have send users a status report stating all timings of EOD processes for all countries.
I need timings for following... (0 Replies)
Discussion started by: ammbhhar
0 Replies
8. HP-UX
Hello,
I have an ancient HP-UX 11.11 system where I have a logical volume marked stale and I can't get it sync'd. I have tried lvsync and lvreduce/lvextend to no avail. It is just one 4Mb PE on the disk that I can't get current.
# lvdisplay -v /dev/vg00/lvol5 | grep stale
LV Status ... (17 Replies)
Discussion started by: port43
17 Replies
9. AIX
Hi friends,
the paging lv hd6 is in stale condition
hd6 paging 48 96 2 open/stale N/A
And i'am getting the following alerts in the server 333BD283 0811044814 U S LVDD Bad block detected with no relocation al
333BD283 0811041114 U S LVDD ... (1 Reply)
Discussion started by: Mohamed Thamim
1 Replies
10. AIX
Hi everybody,
I have a little problem with my AIX 6.1, PowerHA 6.1 LVM mirror. After problem with SAN pathing of our one Datacenter, I have LV at stale state.
# lsvg cpsdata2vg
VOLUME GROUP: cpsdata2vg VG IDENTIFIER: 00fb518c00004c0000000169445f4c2c
VG STATE: ... (6 Replies)
Discussion started by: Necronomic
6 Replies
LEARN ABOUT MOJAVE
shutdown
SHUTDOWN(8) BSD System Manager's Manual SHUTDOWN(8)
NAME
shutdown -- close down the system at a given time
SYNOPSIS
shutdown [-] [-h [-u] | -r | -s | -k] [-o [-n]] time [warning-message ...]
DESCRIPTION
The shutdown utility provides an automated shutdown procedure for super-users to nicely notify users when the system is shutting down, saving
them from system administrators, hackers, and gurus, who would otherwise not bother with such niceties.
The following options are available:
-h The system is halted at the specified time.
-k Kick everybody off. The -k option does not actually halt the system, but leaves the system multi-user with logins disabled (for all
but super-user).
-n If the -o is specified, prevent the file system cache from being flushed by passing -n option to halt(8) or reboot(8). This option
should probably not be used.
-o If -h or -r is specified, shutdown will execute halt(8) or reboot(8) instead of sending a signal to launchd(8).
-r The system is rebooted at the specified time.
-s The system is put to sleep at the specified time.
-u The system is halted up until the point of removing system power, but waits before removing power for 5 minutes so that an external
UPS (uninterruptible power supply) can forcibly remove power. This simulates a dirty shutdown to permit a later automatic power on.
OS X uses this mode automatically with supported UPSs in emergency shutdowns.
time Time is the time at which shutdown will bring the system down and may be the word now (indicating an immediate shutdown) or specify a
future time in one of two formats: +number, or yymmddhhmm, where the year, month, and day may be defaulted to the current system val-
ues. The first form brings the system down in number minutes and the second at the absolute time specified.
warning-message
Any other arguments comprise the warning message that is broadcast to users currently logged into the system.
- If '-' is supplied as an option, the warning message is read from the standard input.
At intervals, becoming more frequent as apocalypse approaches and starting at ten hours before shutdown, warning messages are displayed on
the terminals of all users logged in.
At shutdown time a message is written to the system log, containing the time of shutdown, the person who initiated the shutdown and the rea-
son. Corresponding signal is then sent to launchd(8) to respectively halt, reboot or bring the system down to single-user state (depending
on the above options).
A scheduled shutdown can be canceled by killing the shutdown process (a SIGTERM should suffice).
SIGTERM TO SIGKILL INTERVAL
Upon shutdown, all running processes are sent a SIGTERM followed by a SIGKILL. The SIGKILL will follow the SIGTERM by an intentionally inde-
terminate period of time. Programs are expected to take only enough time to flush all dirty data and exit. Developers are encouraged to
file a bug with the OS vendor, should they encounter an issue with this functionality.
SEE ALSO
kill(1), login(1), wall(1), halt(8), launchd(8), reboot(8)
BACKWARD COMPATIBILITY
The hours and minutes in the second time format may be separated by a colon (``:'') for backward compatibility.
HISTORY
The shutdown utility appeared in 4.0BSD.
BSD
December 11, 1998 BSD