10 More Discussions You Might Find Interesting
1. AIX
Hi all,
I'm getting some errors on AIX regarding Flashcopy and volume group hard disks.
The script that activates flashcopy showed this errors:
Recreating Flashcopy for lun01_A1
Performing syntax check...
Syntax check complete.
Executing script...
Script execution complete.
SMcli... (1 Reply)
Discussion started by: enux
1 Replies
2. UNIX for Dummies Questions & Answers
Hello,
I am looking for help on how to use ghost 4 unix. I know there is a site for ghost 4 unix, but if I understood that I wouldn't be here. Everything is already set up, there is a ftp server, iomega network hard drive, there are already images on this network harddrive. I know how to use the... (0 Replies)
Discussion started by: slakk
0 Replies
3. SCO
Hi.
We tried cloning a SCO Unix hard disk using Norton Ghost.
However, the new cloned hard disk encounter booting problem.
What possibly go wrong? (1 Reply)
Discussion started by: Mizan
1 Replies
4. Solaris
Hi Guru's
Can any want here could explain to me the different between soft reboot and hard reboot .
Best Regards
Seelan (3 Replies)
Discussion started by: seelan3
3 Replies
5. UNIX for Dummies Questions & Answers
I'm trying to delete a folder in my trash that contains no files or hidden files and nothing happens. It is still there.
However, when I try to delete everything in the folder in terminal I receive an error: Ti?ng Viê?t.html: No such file or directory. I can't find this file anywhere on my tiger... (1 Reply)
Discussion started by: jopper
1 Replies
6. AIX
I am having a problem that I cannot figure out. RS6000 server running AIX 5.2. Users connect via TCP/IP and login and work just fine. When the user logs out of the application, I can run the "who" command or "w" command and the O/S still reports the user as logged in.
If I run "ps -tpts/xx"... (2 Replies)
Discussion started by: Docboyeee
2 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have a strange (for me) problem here:
I use stop command to close program. After that I try to start it again. However, it wont start because one of the needed component fails to start. That is caused propably because the failing component is still running (obviously as a ghost pid).... (3 Replies)
Discussion started by: kolada
3 Replies
8. UNIX for Dummies Questions & Answers
I have a Solaris Ultra 10 Box, which contains all my software, I got a new Sun Ultra10 with the same configuration. Can I ghost the it ? Does Unix support any such application. (6 Replies)
Discussion started by: stephen104
6 Replies
9. UNIX for Dummies Questions & Answers
I just noticed by running a who command that I was logged in twice . So two admin2 are on the list. (solaris 2.6)
Since I telnet using a windows 98, I suppose that I forgot to CTRL-D last time I logged in and clicked on hangup.
In such a case, how can I loggoff the old ghost loggin ?
It's not a... (4 Replies)
Discussion started by: phpote
4 Replies
10. UNIX for Dummies Questions & Answers
Hello,
I have problems executing a script in ksh with this script named
process.sh:
ps -ef | grep process.sh | grep -v grep | wc -l | read a
if
then
echo "The script is running"
exit 0
fiThe problem is that when I execute the script, sometimes it shows the
message "The script is... (10 Replies)
Discussion started by: jguirao
10 Replies
reboot(1M) reboot(1M)
NAME
reboot - restart the operating system
SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments]
The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel.
Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending
loss of service. See shutdown(1M) for details.
The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On
systems, reboot may also update the boot archive as needed to ensure a successful reboot.
The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting
file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present.
Normally, the system reboots itself at power-up or after crashes.
The following options are supported:
-d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps.
-l Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot.
-n Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync
filesystems prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to
sync filesystems.
-q Quick. Reboot quickly and ungracefully, without shutting down running processes first.
The following operands are supported:
boot_arguments An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel
upon restart. The form and list of arguments is described in the boot(1M) and kernel(1M) man pages.. If the arguments are
specified, whitespace between them is replaced by single spaces unless the whitespace is quoted for the shell. If the
boot_arguments begin with a hyphen, they must be preceded by the -- delimiter (two hyphens) to denote the end of the reboot
argument list.
Example 1: Passing the -r and -v Arguments to boot
In the following example, the delimiter -- (two hyphens) must be used to separate the options of reboot from the arguments of boot(1M).
example# reboot -dl -- -rv
Example 2: Rebooting Using a Specific Disk and Kernel
The following example reboots using a specific disk and kernel.
example# reboot disk1 kernel.test/unix
/var/adm/wtmpx login accounting file
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
mdb(1), boot(1M), dumpadm(1M), fsck(1M), halt(1M), init(1M), kernel(1M), shutdown(1M), sync(1M), syslogd(1M), sync(2), uadmin(2),
reboot(3C), attributes(5)
The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown
of system services, use shutdown(1M) or init(1M) to reboot a Solaris system.
11 Apr 2005 reboot(1M)