02-11-2011
I ran the pkginfo -p command and the system returned nothing. I also started the OS reinstallation last night, before leaving for the day and it finished up. After rebooting the system this morning the issue remains.
10 More Discussions You Might Find Interesting
1. SCO
Can i change the password on the SCO GUI interface login page and if so how?
When I try to login it just goes right back to the login screen. If anyone has any suggestions, please reply. :confused: (3 Replies)
Discussion started by: qphillips
3 Replies
2. Solaris
Hi experts,
I've installed Solaris 8 to Sunfire V480. After installation I only could login to the server using CLI command. Can you show me how to start the login GUI? I use standard SUN graphic monitor and keyboard.
Thanks in advanced.
VN (26 Replies)
Discussion started by: vntiger
26 Replies
3. Linux
hi
iam installed mandriva spring 2009
iam unble to login into gui using root
how to enable it
where the settings are stored (5 Replies)
Discussion started by: seshumohan
5 Replies
4. Solaris
I have 2 queries:
1.how do we monitor failed GUI logins...? I think the /var/adm/loginlog will log
only failed logins happened at /dev/console and virtual terminals..
2.How to use cron scheduler to display a message when a user is working in GUI Terminal window irrespective of in which... (1 Reply)
Discussion started by: saagar
1 Replies
5. UNIX for Advanced & Expert Users
Hi,
When I installed Ubuntu on my laptop, I had chosen "automatic login" . So i was not asked ofr username and password everytime I switched on. I later wanted to change the settings. So I went to systems-->administration-->login window-->security. There I disabled automatic login and I reboot the... (3 Replies)
Discussion started by: vishwamitra
3 Replies
6. Fedora
Hi all,
I am able to login via putty to a fedora 10 workstation.
But when i try to login via physical screen connected to workstation, it just gives me a blank screen and i cant see any options to enter username and passwd. How do i get the physical GUI to work.
$ who -r
... (4 Replies)
Discussion started by: lramsb4u
4 Replies
7. Solaris
Solaris machine is at # prompt not able to login in GUI mode :
I want to login solaris server in GUI mode from # prompt.
---------- Post updated 12-30-11 at 11:36 AM ---------- Previous update was 12-29-11 at 02:23 PM ----------
Hi,
Please send me some guidelines regarding this....
as... (2 Replies)
Discussion started by: sunray
2 Replies
8. UNIX for Dummies Questions & Answers
I am not too new with linux. Since I installed a new version (2011) of Mandriva, I am unable to login via the gui (I'm currently using the live version of the same dvd free with Linux Format mag). I can login from a console as it has picked up the previous version's /home, but when I try to login... (2 Replies)
Discussion started by: richardmellersh
2 Replies
9. Shell Programming and Scripting
hii all,
I am unable to login into GUI mode in solaris 10. It is only prompting me to command mode credentials not going further to GUI mode.. Please help..
Thanks & regards,
Bhagi (3 Replies)
Discussion started by: bhargav90
3 Replies
10. Solaris
I just got moved to a new office building, and as I was unpacking my stuff I saw an odd tower PC in the nearby recycling heap. It turned out to be a Sun Ultra 10 Elite3D workstation, complete with keyboard, mouse, and monster-sized CRT with the wacky Sun video cable.
I just set everything up and... (4 Replies)
Discussion started by: wowbobwow
4 Replies
REBOOT(8) System Manager's Manual REBOOT(8)
NAME
reboot - stopping and restarting the system
SYNOPSIS
/sbin/reboot [ -lqnhdarsfRD ]
/sbin/halt [ -lqndars ]
/sbin/fastboot [ -lqndarsRD ]
DESCRIPTION
2.11BSD is started by placing it in memory at location zero and transferring to its entry point. Since the system is not reentrant, it is
necessary to read it in from disk or tape each time it is to be boot strapped.
Rebooting a running system: When the system is running and a reboot is desired, shutdown(8) is normally used to stop time sharing and put
the system into single user mode. If there are no users then /sbin/reboot can be used without shutting the system down first.
Reboot normally causes the disks to be synced and allows the system to perform other shutdown activities such as resynchronizing hardware
time-of-day clocks. A multi-user reboot (as described below) is then initiated. This causes a system to be booted and an automatic disk
check to be performed. If all this succeeds without incident, the system is then brought up for multi-user operation.
Options to reboot are:
-l Don't try to tell syslogd(8) what's about to happen.
-q Reboot quickly and ungracefully, without shutting down running processes first.
-n Don't sync before rebooting. This can be used if a disk or the processor is on fire.
-h Don't reboot, simply halt the processor.
-d Dump memory onto the dump device, usually part of swap, before rebooting. The dump is done in the same way as after a panic.
-a Have the system booter ask for the name of the system to be booted, rather than immediately booting the default system (/unix).
-r Mount the root file system as read only when the system reboots. This is not supported by the kernel in 2.11BSD.
-s Don't enter multi-user mode after system has rebooted - stay in single user mode.
-f Fast reboot. Omit the automatic file system consistency check when the system reboots and goes multi-user. This is accomplished by
passing a fast reboot flag on to the rebooting kernel. This currently prevents the use of -f flag in conjunction with the -h (halt)
flag.
-D Set the autoconfig(8) debug flag. This is normally not used unless one is debugging the autoconfig program.
-R Tells the kernel to use the compiled in root device. Normally the system uses the device from which it was booted as the
root/swap/pipe/dump device.
Reboot normally places a shutdown record in the login accounting file /usr/adm/wtmp. This is inhibited if the -q or -n options are
present. Note that the -f (fast reboot) and -n (don't sync) options are contradictory; the request for a fast reboot is ignored in this
case.
Halt and fastboot are synonymous with ``reboot -h'' and ``reboot -f'', respectively.
Power fail and crash recovery: Normally, the system will reboot itself at power-up or after crashes if the contents of low memory are
intact. An automatic consistency check of the file systems will be performed, and unless this fails, the system will resume multi-user
operations.
SEE ALSO
autoconfig(8), sync(2), utmp(8), shutdown(8), syslogd(8)
3rd Berkeley Distribution May 24, 1996 REBOOT(8)