When I join to the only account the server try to launch de Windows Manager (openwin) but this error show:
Code:
/usr/openwin/bin/xinit: Server error.
I login with root and try to start X Window Manager (openwin) manually using:
Code:
shell# cd /usr/openwin/bin/
shell# ./openwin
VUIDFORMAT: Invalid argument
Fatal server error:
Failed to initialize core devices
/usr/openwin/bin/xinit: Server error
I try this second option manually:
Code:
shell# /usr/openwin/bin/openwin -dev /dev/fb
/usr/openwin/bin/xinit: Connection refused (errno 146): unable to connect to X Server
/usr/openwin/bin/xinit: No such process (errno 3): Server error.
For second option I try to "reinstall Solaris 8" using the "original CD's" but when the CD Boot and I select the language and Keyboard, the system tru to launch a window manager but the same error appear "/usr/openwin/bin/xinit: Server error". So, I can't reinstall all the system to
Last edited by siegroup; 07-16-2019 at 12:06 PM..
Reason: add more info...
1.I was trying to use Exceed to run Solaris "openwin" on my Windows 95. I got an error :
/usr/openwin/bin/openwin &
28522
$
/dev/fb: No such file or directory
Graphics Adapter device /dev/fb is of unknown type
Fatal server error:
InitOutput: Error loading module for /dev/fb
Does... (1 Reply)
I have a server that is on solaris 9 and openwin is locked. The mouse won't respond and I can't seem to kill the openwin pid on the server.. Is there a command line to kill openwin from the server side? (2 Replies)
Discussion started by: jphorton
2 Replies
3. Post Here to Contact Site Administrators and Moderators
Hi Gents,
I have downloaded Sol 8 2/04 from Sun's web page and I have tried to install it into a V890. I can boot from a CD 1of 2 without any problem.
After the selection of the language and the Locale, the TWM (Sol Install Console window) cannot starts up. The following are the errors... (0 Replies)
Hi all,
I am a newbies here,
Have question regards large hard disk install in SunBlade system.
Can SunBlade 150 support 2 x 160GB (internal IDE) ?
Want to make sure before buy the hard disks.
Anyone had experiences configure large hard disk in SunBlade 150 before ?
In the SunBlade 150... (2 Replies)
I have a client who is using Solaris 8 and on login the system tris to open windows but then generates the following error
failed to open /usr/openwin/AcceleratedX/etc/Siteinfo
Fatal Server error
Failed to configure the xserver
Help Please!
Thanks (0 Replies)
Solaris 10 on an Ultra 45, there are two serial ports (com A and B) And I need to be able to use an old serial trackball mouse in the openwin dt enviornment. Do I have any options? Even if I have to buy an external device for conversion? Want to configure openwin to use an old serial pointer device... (0 Replies)
I purchased a Sunblade 150 from Ebay. It had 512MB RAM and 80GB hard disk. I recently purchased additional RAM and another 80GB disk, and installed them. The RAM goes through POST without issues. I just can't get beyond the OK prompt. I am using the serial console.
I have been unable to... (5 Replies)
I have several applications locked to Solaris 8 (and older) and have been very happy with my Sparcs and Ultras but am getting tinnitus problems from fans and disks.
Any tips on a quiet thin client (with decent graphics, not video or gaming level but 24bit and multi monitor would be useful) that... (0 Replies)
Discussion started by: batchman
0 Replies
LEARN ABOUT SUSE
ivman-launch
IVMAN-LAUNCH(8) System Manager's Manual IVMAN-LAUNCH(8)NAME
ivman-launch - launch script for Ivman
SYNOPSIS
ivman-launch [ --exit-with-session <cmd> ] [ OPTIONS ] [ COMMAND [ ARGS... ]]
DESCRIPTION
ivman-launch is a simple script used to launch Ivman. Its sole purpose is to ensure Ivman is closed at the end of a user's login session.
You can use it if your session manager does not properly close Ivman when you log out.
ivman-launch supports the same command-line options as Ivman, and one additional option: --exit-with-session. Thus, there is no point
using ivman-launch if you do not need to use this option.
If you supply a COMMAND (with optional ARGS), the the specified command will be run after ivman is started, and ivman will be killed after
that command exits.
OPTIONS --exit-with-session <cmd>
ivman-launch will block until the command 'cmd' terminates, at which point it will kill Ivman and exit itself. If the command 'cmd'
is not running when ivman-launch is started, Ivman will exit immediately. Note that this option implies Ivman will be called with
the '--nofork' option. option.
--debug --nofork --system
These flags be passed to the launched ivman command.
EXAMPLES
ivman-launch --exit-with-session xinit &
The ivman process will be started, then the xinit process is watched. When the xinit process exits, ivman is killed. Placing this
command in an ~/.xinitrc file would cause Ivman to launch in the background when your session begins, and exit when your session
ends:
ivman-launch /usr/bin/x-window-manager
The ivman process is launched, then /usr/bin/x-window-manager is run, when x-window-manager exits, ivman is killed. This is an
example of how ivman might be launched from Xsession in order to chain several programs together in one session.
SEE ALSO ivman(8)Xsession(5)CREDITS
This script was written by Daniele Favara.
10 February 2006 IVMAN-LAUNCH(8)
07-16-2019
