10 More Discussions You Might Find Interesting
1. HP-UX
Hi,
I have exported a few nfs mounts from one server to the nfs clients.
This is my nfs server dfstab :
# cat /etc/dfs/dfstab
# place share(1M) commands here for automatic execution
# on entering init state 3.
#
# share <pathname>
# .e.g,
# share -F... (3 Replies)
Discussion started by: anaigini45
3 Replies
2. How to Post in the The UNIX and Linux Forums
Hi,
I making a script to check nfs mount and unmount options.
After various findings, i didn't get any solution for that.
Can you please help me in making the script.
1) I have used,
if grep -qs '/var/JETSHARE' /proc/mounts; then
echo "It's mounted."
else
echo "It's not mounted.
... (2 Replies)
Discussion started by: Santosh101
2 Replies
3. UNIX for Dummies Questions & Answers
Hi All,
I created a nfs share in the server(Solaris 10) with the following command and also updated the dfstab file
share -F nfs -o rw=server_name2,anon=0 /to_share
And then in the client(solaris 10) added the following command to mount the share
mount -F nfs server_name1:/to_share... (4 Replies)
Discussion started by: Rossdba
4 Replies
4. UNIX and Linux Applications
Hello folks,
I'm remotely connecting through VNC to two machines, each running Red Hat 5.9, from mine which is running Windows 7. Both connections were working well before. However, now one of the machines only gives me a black screen, with a pop up that says:
"There was an error starting... (1 Reply)
Discussion started by: Miguel E. Perez
1 Replies
5. UNIX for Dummies Questions & Answers
Hi
we have couple of nfs mounts between various linux servers. Recently i was wondering how to improve the performance by altering the parameters "msize" and "rsize" for nfs.
In my machine i have determined the NFSSVC_MAXBLKSIZE_V2 = 8*1024 but kernel 2.6 supports upto 32k Optimizing NFS... (0 Replies)
Discussion started by: rakeshkumar
0 Replies
6. Red Hat
Hi,
I have some filesystem which is nfs mounted and shared to other servers.
Nfs server name= nfsserver (here filesystem is locally mounted)
server name where filesystem is shared = sharedserver1 and sharedserver2
filesystem which is shared = /filesystem1
when i am checking utilization by... (1 Reply)
Discussion started by: anshu ranjan
1 Replies
7. Solaris
If I am not a system admin. How can I tell where a particular mounted file is mounted from. (12 Replies)
Discussion started by: Harleyrci
12 Replies
8. Solaris
Hello all,
We're using JET to build our systems.. I'm in the process of needing to build a centrally located JET box with access to all our networks rather that 2 or 3 dotted around. Part of the means I need to locate the boot & OS images on an NFS mount (via NETAPP filer)..
However in the... (1 Reply)
Discussion started by: itsupplies
1 Replies
9. Shell Programming and Scripting
Hello,
I have a backup script that backs up my system to a nfs mounted file system. The mount point on my local system is /backup.
I want my script to check whether the nfs file system is mounted on /backup before actually backing anything up. Even if the nfs file system was NOT mounted,... (2 Replies)
Discussion started by: xadamz23
2 Replies
10. UNIX for Dummies Questions & Answers
I would like to know if there is a command or set of commands that I can run to verify that there are no 'extraneous' nfs mounted filesystems on our server. I didn't see anything in doing a search on NFS.
We think that we may have some filesystems that are still nfs mounted when the link should... (3 Replies)
Discussion started by: giannicello
3 Replies
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)