9 More Discussions You Might Find Interesting
1. Programming
I'm facing an issue in which my program is using a custom library (say, libxyz.so) which is compiled using libstdc++.so.5 and the system I'm using this library to create an executable from my program, has libstdc++so.6 as well as libstdc++.so.5; both available under /usr/lib directory.
There are... (8 Replies)
Discussion started by: Praveen_218
8 Replies
2. HP-UX
I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email.
original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies
3. UNIX for Dummies Questions & Answers
hi guys
I have to install a software that says have theses packages are required
Libaio.so.1
Libstdc++so.6
are these default packages for a Suse 11 installation for instance? or do I need to download them to avoid dependency issues
thanks a lot
---------- Post updated at 10:00 PM... (0 Replies)
Discussion started by: kopper
0 Replies
4. Red Hat
Hi all,
I am working on Red Hat Enterprise Linux ES release 4 (Nahant) with kernel 2.6.9-5 and try to install one application but unable to install it.
When I am trying to install it,it is throwing the following error--
To resolve it,I installed gcc 4.0.0 and when I am trying to see gcc... (2 Replies)
Discussion started by: smartgupta
2 Replies
5. Ubuntu
Hi! I'm using Ubuntu Karmic and I lost libstdc++.so.6. Is there a way to recover it?..
Thanks in advance (0 Replies)
Discussion started by: Sapfeer
0 Replies
6. Shell Programming and Scripting
I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies
7. AIX
hello everybody i am new on the AIX environment and i have faced an issue while running pstill it can't find ibstdc++.a (libstdc++.so.5) although i have the latest GCC and libstdc 4.0.0 i guess.
So to resolve the problem i have got an old versions that i want to install on AIX:
... (5 Replies)
Discussion started by: eternalflame
5 Replies
8. Programming
Our development machines have libstdc++.so.5 and libstdc++.so.6.
When we build our native code, it uses libstdc++.so.6. Is there anyway I can force it to use libstdc++.so.5 instead ?
$ ldd try
/usr/lib/libcwait.so (0x00655000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6... (5 Replies)
Discussion started by: vino
5 Replies
9. HP-UX
To anyone who can help.
I am trying to get VNC running using the inetd capability and I am having problems. I have VNC running fine when I manually log into the server through FTP or SSH and start it and then start the viewer on my PC.
I have tried a few things I have found on different... (0 Replies)
Discussion started by: punkdeviant
0 Replies
LEARN ABOUT DEBIAN
vnc4server
vncserver(1) Virtual Network Computing vncserver(1)
NAME
vncserver - start or stop a VNC server
SYNOPSIS
vncserver [:display#] [-name desktop-name] [-geometry widthxheight] [-depth depth] [-pixelformat format] [Xvnc-options...]
vncserver -kill :display#
DESCRIPTION
vncserver is used to start a VNC (Virtual Network Computing) desktop. vncserver is a Perl script which simplifies the process of starting
an Xvnc server. It runs Xvnc with appropriate options and starts some X applications to be displayed in the VNC desktop.
vncserver can be run with no options at all. In this case it will choose the first available display number (usually :1), start Xvnc as
that display, and run a couple of basic applications to get you started. You can also specify the display number, in which case it will use
that number if it is available and exit if not, eg:
vncserver :13
Editing the file $HOME/.vnc/xstartup allows you to change the applications run at startup (but note that this will not affect an existing
desktop).
OPTIONS
You can get a list of options by giving -h as an option to vncserver. In addition to the options listed below, any unrecognised options
will be passed to Xvnc - see the Xvnc man page, or "Xvnc -help" for details.
-name desktop-name
Each desktop has a name which may be displayed by the viewer. It defaults to "host:display# (username)" but you can change it with
this option. It is passed in to the xstartup script via the $VNCDESKTOP environment variable, allowing you to run a different set
of applications according to the name of the desktop.
-geometry widthxheight
Specify the size of the desktop to be created. Default is 1024x768. Can be specified as an array or scalar for geometry.
-depth depth
Specify the pixel depth in bits of the desktop to be created. Default is 16, other possible values are 8, 15 and 24 - anything else
is likely to cause strange behaviour by applications.
-pixelformat format
Specify pixel format for server to use (BGRnnn or RGBnnn). The default for depth 8 is BGR233 (meaning the most significant two bits
represent blue, the next three green, and the least significant three represent red), the default for depth 16 is RGB565 and for
depth 24 is RGB888.
-cc 3 As an alternative to the default TrueColor visual, this allows you to run an Xvnc server with a PseudoColor visual (i.e. one which
uses a colour map or palette), which can be useful for running some old X applications which only work on such a display. Values
other than 3 (PseudoColor) and 4 (TrueColor) for the -cc option may result in strange behaviour, and PseudoColor desktops must be 8
bits deep.
-kill :display#
This kills a VNC desktop previously started with vncserver. It does this by killing the Xvnc process, whose process ID is stored in
the file "$HOME/.vnc/host:display#.pid". It actually ignores anything preceding a ":" in its argument. This can be useful so you
can write "vncserver -kill $DISPLAY", for example at the end of your xstartup file after a particular application exits.
FILES
Several VNC-related files are found in the directory $HOME/.vnc:
$HOME/.vnc/xstartup
A shell script specifying X applications to be run when a VNC desktop is started. If it doesn't exist, vncserver will create a new
one which runs a couple of basic applications.
$HOME/.vnc/passwd
The VNC password file.
$HOME/.vnc/host:display#.log
The log file for Xvnc and applications started in xstartup.
$HOME/.vnc/host:display#.pid
Identifies the Xvnc process ID, used by the -kill option.
SEE ALSO
vncviewer(1), vncpasswd(1), vncconfig(1), Xvnc(1)
http://www.realvnc.com
AUTHOR
Tristan Richardson, RealVNC Ltd.
VNC was originally developed by the RealVNC team while at Olivetti Research Ltd / AT&T Laboratories Cambridge. It is now being maintained
by RealVNC Ltd. See http://www.realvnc.com for details.
RealVNC Ltd 03 Mar 2005 vncserver(1)