Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Rdesktop failed to open keymap common#015 Post 302369699 by TonyFullerMalv on Monday 9th of November 2009 09:57:36 AM
Old 11-09-2009
Permission? Chmod it to 644 and the holding directory to 755 perhaps?
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Failed to open output file Error

Hi guys, I Have written a script,In that it will call another file which contains the sql quaries. while wxecuting that I am getting the below exception 01/16|06:28:06:16800: Operating System Error|Failed to open output file Can anybody help me about this,,Its urgent (0 Replies)
Discussion started by: Anji
0 Replies

2. Solaris

libCstd.so.1: open failed

Morning all, I have a problem with a Sun workstation which is running Solaris 8. When I attempt to open an application, the executable fails with this message : "fatal: libcstd.so.1: open failed: No such file or directory" It was suggested to me that I need to add these patches to fix the... (4 Replies)
Discussion started by: AndyD
4 Replies

3. Solaris

Error:: libm.so.2:open failed

Hi, I am working with solaris 9 and I want to install perforce on that,so I downloaded the p4v.bin file and try to install it by the command ./p4v after that it is giving the error--- ld.so.1: ./p4v.bin: fatal: libm.so.2: open failed: No such file or directory Killed I am not... (3 Replies)
Discussion started by: smartgupta
3 Replies

4. Solaris

Solaris10..Open boot diagnostic failed

Hi all, when am rebooting the server (SF v890) we are facing "open boot diagnostic failed". Thanks in Adv. (5 Replies)
Discussion started by: arjunreddy3
5 Replies

5. Solaris

libucb.s0.1: open failed...

Hi all. I try to start an application, but libucb.so1 is missing. # appl23 # appl23ld.so.1: appl23: fatal: libucb.so1: open failed: No such file or directory killed # # ldd appl23 libXm.so.3 => /usr/lib/libXm.so.3 libMrm.so.3 => /usr/lib/libMrm.so.3 ... (14 Replies)
Discussion started by: wolfgang
14 Replies

6. Ubuntu

Failed to install Common Array Manager in Ubuntu

Dear All, I have a problem installing SUN CAM on my laptop running Ubuntu 9.04 The error message is : Failed when detecting Sun StorageTek(TM) Common Array Manager Core Components : Could not convert Pkg version : For input string: "" Any idea why? Best regards (0 Replies)
Discussion started by: frankoko
0 Replies

7. UNIX for Dummies Questions & Answers

NDM: Source file open failed. Error= 2

Hi, I have try to ndm to one server to another server. but i am getting this error. what is this error? are files not in source folder? Source file open failed. Error= 2 Regards, Balamurgan (1 Reply)
Discussion started by: krbala1985
1 Replies

8. Red Hat

rpmdb open failed

Hi, # yum --skip-broken -y update rpmdb: Thread/process 6657/3078387392 failed: Thread died in Berkeley DB library error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db3 - (-30974) error: cannot open... (3 Replies)
Discussion started by: sef alislam
3 Replies

9. Solaris

Sendmai l: libssl.so.0.9.7: open failed

Hey for some reason I think I deleted a critical file for sendmail. I was looking the log file on /var/log/cron for cron, and the file isn't there and I found out the reason why is because I'm missing libssl.so.0.9.7. Im running Solaris 11. I checked smtp and got the following: #svcs -xv... (3 Replies)
Discussion started by: picolin
3 Replies

10. UNIX for Beginners Questions & Answers

Rdesktop - ERROR: Failed to open keymap en-us

I just updated my rdesktop to 1.8.3 from source ( on Slackware 11 ) and had troubles with arrow keys/page up/page down not working. I see this on the console: ERROR: Failed to open keymap en-us The fix is a permission change. I initially looked at /usr/share/rdesktop/keymaps and everything... (1 Reply)
Discussion started by: agentrnge
1 Replies
xon(1X) 																   xon(1X)

NAME
xon - start an X program on a remote machine SYNOPSIS
xon remote-host [-access] [-debug] [-name window-name] [-nols] [-screen screen-no] [-user user-name] [command...] OPTIONS
Note that the options follow the remote host name (as they do with rlogin). Runs xhost locally to add the remote host to the host access list in the X server. This will not work unless xhost is given permission to modify the access list. Normally, xon disconnects the remote process from stdin, stdout and stderr to eliminate the daemon processes which usually connect them across the network. Specifying the -debug option leaves them connected so that error messages from the remote execution are sent back to the originating host. This specifies a different application name and window title for the default command (xterm). Normally xon passes the -ls option to the remote xterm; this option suspends that behaviour. This changes the screen number of the DISPLAY variable passed to the remote command. By default, xon simply uses rsh/remsh/rcmd to connect to the remote machine using the same user name as on the local machine. This option cause xon to specify an alternative user name. This will not work unless you have authorization to access the remote account, by placing an appropriate entry in the remote users file. DESCRIPTION
The xon program runs the specified command (default xterm -ls) on the remote machine using rsh, remsh, or rcmd. xon passes the DISPLAY, XAUTHORITY and XUSERFILESEARCHPATH environment variables to the remote command. When no command is specified, xon runs 'xterm -ls'. It additionally specifies the application name to be 'xterm-remote-host' and the win- dow title to be 'remote-host'. xon can only work when the remote host will allow you to log in without a password, by having an entry in the file permitting access. BUGS
xon can get easily confused when the remote-host, user-name or various environment variable values contain white space. xon has no way to send the appropriate X authorization information to the remote host. xon(1X)
All times are GMT -4. The time now is 05:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy