10 More Discussions You Might Find Interesting
I canīt get a remote desktop login through CDE only with root user.
There are messages in the Xerror file:
/usr/bin/X11/xset: bad font path element (#0), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font... (5 Replies)
Discussion started by: the0m3n
2. UNIX for Dummies Questions & Answers
Hi, can somebody please, please help me?
After a power loss and server restart my server running AIX 4.2.2 could not boot. Following the procedure in my user guide
I checked the hd's with
# fsck -y /dev/hd1
# fsck -y /dev/hd2
# fsck -y /dev/hd3
# fsck -y /dev/hd4
# fsck -y /dev/hd9var
... (4 Replies)
Discussion started by: semso
I had this problem initially with HPUX 11.23, all users including root could not login via CDE or telnet. Then after some workarounds, it resolved by resetting root password via console login. After enabling back all users to login normally (via CDE or telnet), only root can not... (4 Replies)
Discussion started by: irda
I am in a strange situation where I have install the Solaris 10 5/08 OS on Netra 1280 server. When I connect it through my laptop so that I can take the GUI from xmanager. When I try to login as root or any other users also through Java Destop Environment which accepted it after few... (3 Replies)
Discussion started by: girish.batra
5. UNIX for Advanced & Expert Users
I'm having problem with the CDE pre login banner.
I configured the c/usr/dt/config/C/Xresources file to add my warning message:
Dtlogin*greeting.labelString: My Banner
I then modified the Dtlogin*greeting*fontList to display the message in smaller text. This did not work.
... (1 Reply)
Discussion started by: equismorio
When we as normal user try to login, the session startup terminates and we are presented with the login screen.The root user is able to login without any problem.I can log in to the Aix server as normal user through telnet & using xmanager but not directly through server terminal .The Aix version... (1 Reply)
Discussion started by: ranadeep
I have SunBlade 150 Workstation (Solaris 9), I installed the OS again then when I try to login to any server using ( Options > Remote Login > Enter Host Name)
after I entered any host name nothing happened just white page for 2 or 3 mintues then the login screen reseted to the local... (4 Replies)
Discussion started by: adel8483
I've just completed a fresh install of HP-UX 11.0 on my 712/80 and everything starts up fine until it gets to the point where X kicks off and I believe at this point is supposed to launch into the CDE login.
It just sits there on the blank X screen with the X cursor for a minute or so then BEEPS... (9 Replies)
Discussion started by: ErikTheHAck
I m facing a problem that, i m not able to login as root user on cde on hp-ux 11.00, i can login as root on commond line as well as telnet. Thanks in Advance for help.
Awadhesh (2 Replies)
Discussion started by: Awadhesh
10. UNIX for Dummies Questions & Answers
Hi, I'm new to the whole X-windows environment.
Need help please..
Believe it or not- I have a licensed "Reflection".
I use the XDMCP host, and I can see 4 servers there.
2 of the servers are aix servers: one is ver 4.3, the other one is ver 5.
When I open a session to the aix4.3 a large... (2 Replies)
Discussion started by: sunbird
reboot - restart the operating system
/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
-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
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),
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)