05-24-2010
I have no clue about what you tried.
10 More Discussions You Might Find Interesting
1. Solaris
Hi all,
My Ultra 10, running Solaris 8, is giving me problems :( Currently, whenever it boots, the Xserver will not come up, saying "Xserver cannot be started on display 0".
I thought this might have something to do with OWconfig, and so poked it a little (moving params onto different... (5 Replies)
Discussion started by: Gravity
5 Replies
2. UNIX for Dummies Questions & Answers
I have just installed Solaris 10 x86 version on a Compaq Evo desktop station with a Sun 19" SVGA monitor model # CM751U. The desktop has 256MB RAM. The video card is a nVidia Riva TNT2 64. If I do a scanpci command; it returns the card as a nVidia Corporation NV6 (Vanta/Vanta LT)
The Xserver... (1 Reply)
Discussion started by: sjteng
1 Replies
3. UNIX for Advanced & Expert Users
I've recently patched my AIX box from ML02 to ML06 and somehow along the way the monitor no longer starts up in GUI mode.
Running the command xinit gives me the following errros
ioctl Bad file Number
1356- Unable to start the X server
I've checked the path variables, the monitor, the lai0... (0 Replies)
Discussion started by: mahartle
0 Replies
4. UNIX for Dummies Questions & Answers
Hello , im not sure if its the right forum... im sorry if not
im working with putty allot , but now I started to work with more graphical applications and
im looking for free simple and fast Xserver to remote connection, can someone recommend me
if there is something like that ? (3 Replies)
Discussion started by: umen
3 Replies
5. Solaris
Dear
When I restart the Xserver it works fine for less than half an hour and throw this error afterward.
After setting the display DISPLAY=10.195.2.13:0.0, I tried to run xclock. After few minutes it throws this error message
"X connection to 10.195.2.13:0.0 broken (explicit kill or... (0 Replies)
Discussion started by: tanvirscsa
0 Replies
6. UNIX for Advanced & Expert Users
Hi,
From my workstation (win XP)I open a telnet session on Linux(Red Hat) server.
When I issue :
# xclock
I have :
Error: Can't open display:
Then :
# export DISPLAY=192.16.1.87:0.0
# xclock
Error: Can't open display: 192.16.1.87:0.0
Do you have an idea ?
Many thanks. (6 Replies)
Discussion started by: big123456
6 Replies
7. Solaris
I have problem with my V490 server which running on solaris 8. The error show on log file
X_mkdir: nosuch file or directory
Fatal server error:
Failed to establish all listening sockets
error (pid 299): server unexpectedly died
error (pid 299): server for display :0 cant be started
... (1 Reply)
Discussion started by: shamsul
1 Replies
8. UNIX for Dummies Questions & Answers
Hi,
After I remove the external video card after setup, Centos 5.4 upon boot cannot start the XServer for the onboard video card. How can I configure XServer to get it working? Machine is a DELL OPTIPLEX 745 (1 Reply)
Discussion started by: mojoman
1 Replies
9. Solaris
I have this Xserver not display issues, I try search from the forum but found out it can have different errors from the Xerrors logs. Here I upload and hope admin can help.
root@ccs # more Xerrors
The loadable module for the display device SUNWast is not installed.
Fatal server error:... (1 Reply)
Discussion started by: mailbox80
1 Replies
10. UNIX for Advanced & Expert Users
I am administering an Xserver v10.6.8 and I updated the ports using Macports self update. I received this error when calling the program R
dyld: Library not loaded: /opt/local/lib/libicuuc.48.dylib
Referenced from: /opt/local/lib/R/lib/x86_64/libR.dylib
Reason: image not found
Trace/BPT... (2 Replies)
Discussion started by: godzilla07
2 Replies
LEARN ABOUT NETBSD
rump_sp
RUMP_SP(7) BSD Miscellaneous Information Manual RUMP_SP(7)
NAME
rump_sp -- rump remote system call support
DESCRIPTION
The rump_sp facility allows clients to attach to a rump kernel server over a socket and perform system calls. While making a local rump sys-
tem call is faster than calling the host kernel, a remote system call over a socket is slower. This facility is therefore meant mostly for
operations which are not performance critical, such as configuration of a rump kernel server.
Clients
The NetBSD base system comes with multiple preinstalled clients which can be used to configure a rump kernel and request diagnostic informa-
tion. These clients run as hybrids partially in the host system and partially against the rump kernel. For example, network-related clients
will typically avoid making any file system related system calls against the rump kernel, since it is not guaranteed that a rump network
server has file system support. Another example is DNS: since a rump server very rarely has a DNS service configured, host networking is
used to do DNS lookups.
Some examples of clients include rump.ifconfig which configures interfaces, rump.sysctl which is used to access the sysctl(7) namespace and
rump.traceroute which is used to display a network trace starting from the rump kernel.
Also, almost any unmodified dynamically linked application (for example telnet(1) or ls(1)) can be used as a rump kernel client with the help
of system call hijacking. See rumphijack(3) for more information.
Connecting to the server
A remote rump server is specified using an URL. Currently two types of URLs are supported: TCP and local domain sockets. The TCP URL is of
the format tcp://ip.address:port/ and the local domain URL is unix://path. The latter can accept relative or absolute paths. Note that
absolute paths require three leading slashes.
To preserve the standard usage of the rump clients' counterparts the environment variable RUMP_SERVER is used to specify the server URL. To
keep track of which rump kernel the current shell is using, modifying the shell prompt is recommended -- this is analoguous to the visual
clue you have when you login from one machine to another.
Client credentials and access control
The current scheme gives all connecting clients root credentials. It is recommended to take precautions which prevent unauthorized access.
For a unix domain socket it is enough to prevent access to the socket using file system permissions. For TCP/IP sockets the only available
means is to prevent network access to the socket with the use of firewalls. More fine-grained access control based on cryptographic creden-
tials may be implemented at a future date.
EXAMPLES
Get a list of file systems supported by a rump kernel server (in case that particular server does not support file systems, an error will be
returned):
$ env RUMP_SERVER=unix://sock rump.sysctl vfs.generic.fstypes
SEE ALSO
rump_server(1), rump(3), rumpclient(3), rumphijack(3)
HISTORY
rump_sp first appeared in NetBSD 6.0.
BSD
February 7, 2011 BSD