Sponsored Content
Full Discussion: Can't start nfs server!
Top Forums UNIX for Dummies Questions & Answers Can't start nfs server! Post 41794 by Perderabo on Tuesday 14th of October 2003 05:07:43 PM
Old 10-14-2003
This is a real longshot, but check
/etc/net/ticlts/hosts
/etc/net/ticots/hosts
/etc/net/ticotsord/hosts

All three should have the name of the box.
 

9 More Discussions You Might Find Interesting

1. Solaris

NFS write failed for server.....error 11 (RPC: Server can't decode arguments)

Hello! I have a Linux nfs server (called server100 below) with a export nfs. My problem is that the Solaris client (called client100 below) doesn't seems to like it. In the Solaris syslog I got following messages (and after a while the solaris client behave liked its hanged/to buzy). Also see... (3 Replies)
Discussion started by: sap4ever
3 Replies

2. AIX

How to start/stop/restart NFS on AIX

Hi, Very new to aix How to start/stop/restart NFS on AIX thanks, (2 Replies)
Discussion started by: jredx
2 Replies

3. AIX

NFS won't work till I start HACMP

Hi, My NFS does not work till I start HACMP. The NFS service is indeed started when server starts. But it is not in active state, when I use lssrc to check NFS services' status I find they are all in inoperative status. But after I start HACMP (smitty clstart), all NFS services become active... (4 Replies)
Discussion started by: qiulang
4 Replies

4. Solaris

Solaris 9 as a nfs client -- centos as a nfs server.

Hello, I have a centos as nfs server, its name is centos_A. After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/* But, My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies

5. Red Hat

NFS does not start during boot process

Hello, I am facing some issues during boot process of rhel 6.2 It takes too long time (~10 min) for the node to come up... The boot process stuck while it trying to start NFS and does not continue until timeout. In the boot.log file i see Starting NFS quotas: Cannot register service:... (2 Replies)
Discussion started by: @dagio
2 Replies

6. Red Hat

No reponse to 'service NFS start' command

Hello, I have a newly kickstarted RHEL 6.4 server that I'm trying to set-up as a kickstart server. I have done this before on other machines, but I am encountering some strange behaviour in this one. # service nfs status rpc.svcgssd is stopped rpc.mountd is stopped nfsd is stopped... (0 Replies)
Discussion started by: Chopstyx
0 Replies

7. Solaris

Configuration of jump start/NFS server for sol10/sol11 OS installation.

Hi folks, Is it possible to configure Solaris OS install server with NFS method and flar images? I want to configure a kind of jump start server to install flar images. Since there is no support for flar images in soalris11, It is possible to configure single server to install OS on both... (2 Replies)
Discussion started by: Vaishey
2 Replies

8. AIX

AIX NFS Server and NFS Client

Hi 2 ALL, try to run NFS Server in AIX 7.1 : 1. Step by step on NFS Server node mkdir /tmp/test chgrp staff /tmp/test chmod 775 /tmp/test-- create export directory (fs) mknfsexp -d /tmp/test -t ro exportfs -va show mount -e :/# exportfs -av exports: 1831-187 re-exported /tmp/test... (4 Replies)
Discussion started by: penchev
4 Replies

9. UNIX and Linux Applications

Is it mandatory or not to stop/start Applcation server ehen Restarting Database Server?

Good afternoon I need your help please. There is a Mantenance Windos which needs to Restart de Database Server 192.x.x.97 to set up some configuration Is it mandatory or not to stop/start Applcation server that runs in 192.x.x.95 ? Is it mandatory or not to stop/start apache and Tomcat?... (3 Replies)
Discussion started by: alexcol
3 Replies
ticlts(7D)							      Devices								ticlts(7D)

NAME
ticlts, ticots, ticotsord - loopback transport providers SYNOPSIS
#include <sys/ticlts.h> #include <sys/ticots.h> #include <sys/ticotsord.h> DESCRIPTION
The devices known as ticlts, ticots, and ticotsord are ``loopback transport providers,'' that is, stand-alone networks at the transport level. Loopback transport providers are transport providers in every sense except one: only one host (the local machine) is ``connected to'' a loopback network. Loopback transports present a TPI (STREAMS-level) interface to application processes and are intended to be accessed via the TLI (application-level) interface. They are implemented as clone devices and support address spaces consisting of ``flex- addresses,'' that is, arbitrary sequences of octets of length > 0, represented by a netbuf structure. ticlts is a datagram-mode transport provider. It offers (connectionless) service of type T_CLTS. Its default address size is TCL_DEFAULTAD- DRSZ. ticlts prints the following error messages (see t_rcvuderr(3NSL)): TCL_BADADDR bad address specification TCL_BADOPT bad option specification TCL_NOPEER bound TCL_PEERBADSTATE peer in wrong state ticots is a virtual circuit-mode transport provider. It offers (connection-oriented) service of type T_COTS. Its default address size is TCO_DEFAULTADDRSZ. ticots prints the following disconnect messages (see t_rcvdis(3NSL)): TCO_NOPEER no listener on destination address TCO_PEERNOROOMONQ peer has no room on connect queue TCO_PEERBADSTATE peer in wrong state TCO_PEERINITIATED peer-initiated disconnect TCO_PROVIDERINITIATED provider-initiated disconnect ticotsord is a virtual circuit-mode transport provider, offering service of type T_COTS_ORD (connection-oriented service with orderly release). Its default address size is TCOO_DEFAULTADDRSZ. ticotsord prints the following disconnect messages (see t_rcvdis(3NSL)): TCOO_NOPEER no listener on destination address TCOO_PEERNOROOMONQ peer has no room on connect queue TCOO_PEERBADSTATE peer in wrong state TCOO_PEERINITIATED provider-initiated disconnect TCOO_PROVIDERINITIATED peer-initiated disconnect USAGE
Loopback transports support a local IPC mechanism through the TLI interface. Applications implemented in a transport provider-independent manner on a client-server model using this IPC are transparently transportable to networked environments. Transport provider-independent applications must not include the headers listed in the synopsis section above. In particular, the options are (like all transport provider options) provider dependent. ticlts and ticots support the same service types (T_CLTS and T_COTS) supported by the OSI transport-level model. ticotsord supports the same service type (T_COTSORD) supported by the TCP/IP model. FILES
/dev/ticlts /dev/ticots /dev/ticotsord SEE ALSO
t_rcvdis(3NSL), t_rcvuderr(3NSL) SunOS 5.10 3 Jul 1990 ticlts(7D)
All times are GMT -4. The time now is 04:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy