02-26-2016
The connectivity is over fiber channel
9 More Discussions You Might Find Interesting
1. Solaris
I have this problem when i integrate a new san switch in DFM 3.01 R1 :
dfm fcswitch add switchname1
Error: Host switchname2 (11197) already exists.
switchname2 is a similar san switch but in another fabric, switchname2 is already integrated in DFM database.
Bests Regards
Olivier (2 Replies)
Discussion started by: omainfroy
2 Replies
2. UNIX for Dummies Questions & Answers
getting "NFS mount: netapp : RPC: Program not registered" error
searched the site but none of the fixes from previous threads are helping (2 Replies)
Discussion started by: calamine
2 Replies
3. Solaris
Hi there,
I am trying to mount a SAN volume (which is mapped to solaris sparc) partitioned with ufs filesystem onto a linux (intel processor 64bit) server.
*I have re-compiled the linux kernel t support ufs fstype with ro mount support.
filesystem on solaris:... (3 Replies)
Discussion started by: ilan
3 Replies
4. Solaris
Hi,
I've just edited this post. I found the solution for this. Thanks. (0 Replies)
Discussion started by: gwhelan
0 Replies
5. Solaris
Hi all
We have a couple of solaris zones running a jboss app in a cluster. Each zone has a shared netapp volume mounted to /app/xxx with everything under that subdir apart from jboss which is local to each zone in /app/jboss-3.2.5
There is a symlink in /app/xxx/jboss-3.2.5 which points to... (0 Replies)
Discussion started by: skewbie
0 Replies
6. Solaris
Hi
When trying to mount a database from Solaris, we get the error:
Feb 10 09:27:22 SUNTEST nfs: NFS lookup failed for server netapp: error 11 (RPC: Server can't decode arguments)
Feb 10 09:27:27 SUNTEST nfs: NFS getattr failed for server netapp: error 11 (RPC: Server can't decode... (0 Replies)
Discussion started by: wbdevilliers
0 Replies
7. AIX
Hi guys,
I'm trying to mount a windows share (hosted on a NetApp filer with clustered Ontap 8.3) and I have no luck doing it.
This worked before when we used an old NetApp with Ontap 7.3.
Seems there is an issue with ASCII/non-unicode support.
I'm wondering if anybody here has mounted... (7 Replies)
Discussion started by: mikedavis
7 Replies
8. Red Hat
Hi
I have the following difficulty:
the NetApp admin has clone one file system from one red hatserver and presented this cloned LUN into another redhat server.
I can see the LUN as:
fdisk -l
Disk /dev/sda: 64.4 GB, 64424509440 bytes
255 heads, 63 sectors/track, 7832 cylinders
Units =... (1 Reply)
Discussion started by: fretagi
1 Replies
9. Solaris
I have a Solaris 10 server, I'm trying to mount a share from a Windows nfs server. If I add this entry (tst-walnut:/test_sap_nfs - /majid nfs - yes rw,soft) to my /etc/vfstab, then I can mount, but when I create a file by root:root, the file owner changes to... (1 Reply)
Discussion started by: Hiroshi
1 Replies
LEARN ABOUT OPENDARWIN
tcl_setstdchannel
Tcl_GetStdChannel(3) Tcl Library Procedures Tcl_GetStdChannel(3)
__________________________________________________________________________________________________________________________________________________
NAME
Tcl_GetStdChannel, Tcl_SetStdChannel - procedures for retrieving and replacing the standard channels
SYNOPSIS
#include <tcl.h>
Tcl_Channel
Tcl_GetStdChannel(type)
Tcl_SetStdChannel(channel, type)
ARGUMENTS
int type (in) The identifier for the standard channel to retrieve or modify. Must be one of TCL_STDIN, TCL_STDOUT, or
TCL_STDERR.
Tcl_Channel channel (in) The channel to use as the new value for the specified standard channel.
_________________________________________________________________
DESCRIPTION
Tcl defines three special channels that are used by various I/O related commands if no other channels are specified. The standard input
channel has a channel name of stdin and is used by read and gets. The standard output channel is named stdout and is used by puts. The
standard error channel is named stderr and is used for reporting errors. In addition, the standard channels are inherited by any child
processes created using exec or open in the absence of any other redirections.
The standard channels are actually aliases for other normal channels. The current channel associated with a standard channel can be
retrieved by calling Tcl_GetStdChannel with one of TCL_STDIN, TCL_STDOUT, or TCL_STDERR as the type. The return value will be a valid
channel, or NULL.
A new channel can be set for the standard channel specified by type by calling Tcl_SetStdChannel with a new channel or NULL in the channel
argument. If the specified channel is closed by a later call to Tcl_Close, then the corresponding standard channel will automatically be
set to NULL.
If Tcl_GetStdChannel is called before Tcl_SetStdChannel, Tcl will construct a new channel to wrap the appropriate platform-specific stan-
dard file handle. If Tcl_SetStdChannel is called before Tcl_GetStdChannel, then the default channel will not be created.
If one of the standard channels is set to NULL, either by calling Tcl_SetStdChannel with a NULL channel argument, or by calling Tcl_Close
on the channel, then the next call to Tcl_CreateChannel will automatically set the standard channel with the newly created channel. If
more than one standard channel is NULL, then the standard channels will be assigned starting with standard input, followed by standard out-
put, with standard error being last.
See Tcl_StandardChannels for a general treatise about standard channels and the behaviour of the Tcl library with regard to them.
SEE ALSO
Tcl_Close(3), Tcl_CreateChannel(3), Tcl_Main(3), tclsh(1)
KEYWORDS
standard channel, standard input, standard output, standard error
Tcl 7.5 Tcl_GetStdChannel(3)