Sponsored Content
Full Discussion: Timeout Error
Top Forums UNIX for Dummies Questions & Answers Timeout Error Post 23556 by RTM on Tuesday 25th of June 2002 09:29:12 AM
Old 06-25-2002
Perderabo - for a non-OBP expert you do pretty good.

Merlin - the system is definitely attempting to boot from the net. Perderabo's explaination is correct. The install may have changed the default boot device.

SUNSolve OBP commands

You can also do a reset of the OBP back to factory default by turning off power, turn on power while holding down the Stop and N key.
 

10 More Discussions You Might Find Interesting

1. HP-UX

timeout

How can I kick a user out after being idle for a certain amount of time, would prefer not to use scripts, will TMOUT work on HP-UX? (5 Replies)
Discussion started by: csaunders
5 Replies

2. Solaris

About the Timeout

Hello everyone I am a new one,I want to know how to get the solaris force the loginer out if he do not in a time thanks (4 Replies)
Discussion started by: lyh003473
4 Replies

3. UNIX for Advanced & Expert Users

Timeout waiting for arp/rarp error

hello folks, I am trying to install solaris 10 through network using jumpstart but the thing is i am facing problem with the following message problem Timeout waiting for arp/rarp i made sure everything correct as /etc/hosts and /etc/ethers cables are connected, plz anyone help me out (7 Replies)
Discussion started by: solar10
7 Replies

4. Linux

RSH Timeout

Hi All I have a nice little script that i have written in Perl, in it use RSH ( yes i know it is i should being using ssh, but it i secure network it is being run on) the idea of the script it that it will RSH into a machine and then follow out a command, the problem i am running into is if the... (3 Replies)
Discussion started by: John101
3 Replies

5. Solaris

SFTP is successful but still shows timeout error

Hi, I am doing sftp from remote server1 to remote server2. This is done through a script. This script was working fine. But if i am tranfer files of 120 MB only some part of the file gets transferred (around 9 MB). Incase i put the same file manually it gets uploaded successfully. Can... (1 Reply)
Discussion started by: subiksha
1 Replies

6. Programming

using libpcap with timeout

I want to write a small application using Libpcap in C on Linux. Currently, it starts to sniff and waits for the packets. But that's not what I need actually. I want it to wait for N seconds and then stop listening. (I think there's something wrong with my usage of 'pcap_open_live'...) How... (0 Replies)
Discussion started by: xyzt
0 Replies

7. Shell Programming and Scripting

Timeout in shellscripting

#!/bin/sh for ip in $(cat /root/Desktop/ftp.txt) do HOST=$ip USER='bob' PASS='bob' ftp -n $HOST <<EOF user bob bob EOF echo "$ip" done the Above code i want to use check and verify login works on multiple ftp servers on my network. However the ftp servers are dynamic in setup... (5 Replies)
Discussion started by: Noledge
5 Replies

8. Red Hat

TNS Timeout Error when connecting to SQLPLUS through scripts only

Hi, I am facing a strange issue when connecting to SQLPLUS via a shell scripts. I am using Linux 2.6.18-274.18.1 and gbash shell. When I connect to SQLPLUS through scripts then it throws TNS Time Out error ""sometimes"" and connects successfully other times.This is only happening when... (9 Replies)
Discussion started by: aashish.sharma8
9 Replies

9. Solaris

weblogic connection timeout error

i am facing an issue that the server give a connection timeout after 60 sec for any request more than that number . i tried to increase the TCP INTERVAL TIMEOUT from the default 60000 ms to more higher number. the server seems to work fine and didn't give me the massage of the timeout but the... (0 Replies)
Discussion started by: core99
0 Replies

10. Shell Programming and Scripting

What is this error log = hda: irq timeout: error=0x00 and how to solve?

what is this error log = hda: irq timeout: error=0x00 and how to solve? every day upon checking the logs i see this error. hda: irq timeout: error=0x00 hda: irq timeout: error=0x00 hda: irq timeout: error=0x00 hda: irq timeout: error=0x00 hw_client: segfault at 0000000000000046 rip... (3 Replies)
Discussion started by: avtalan
3 Replies
ssh_connection(3erl)					     Erlang Module Definition					      ssh_connection(3erl)

NAME
ssh_connection - This module provides an API to the ssh connection protocol. DESCRIPTION
This module provides an API to the ssh connection protocol. Not all features of the connection protocol are officially supported yet. Only the ones supported are documented here. COMMON DATA TYPES
Type definitions that are used more than once in this module and/or abstractions to indicate the intended use of the data type: boolean() = true | false string() = list of ASCII characters timeout() = infinity | integer() - in milliseconds. ssh_connection_ref() - opaque to the user returned by ssh:connect/3 or sent to a ssh channel processes ssh_channel_id() = integer() ssh_data_type_code() = 1 ("stderr") | 0 ("normal") are currently valid values see RFC 4254 section 5.2. ssh_request_status() = success | failure MESSAGES SENT TO CHANNEL PROCESSES
As a result of the ssh connection protocol messages on the form {ssh_cm, ssh_connection_ref(), term()} will be sent to a channel process. The term will contain information regarding the ssh connection protocol event, for details see the ssh channel behavior callback han- dle_ssh_msg/2 EXPORTS
adjust_window(ConnectionRef, ChannelId, NumOfBytes) -> ok Types ConnectionRef = ssh_connection_ref() ChannelId = ssh_channel_id() NumOfBytes = integer() Adjusts the ssh flowcontrol window. Note: This will be taken care of by the ssh_channel behavior when the callback handle_ssh_msg/2 has returned after processing a {ssh_cm, ssh_con- nection_ref(), {data, ssh_channel_id(), ssh_data_type_code(), binary()}} message, and should normally not be called explicitly. close(ConnectionRef, ChannelId) -> ok Types ConnectionRef = ssh_connection_ref() ChannelId = ssh_channel_id() Sends a close message on the channel ChannelId Note: This function will be called by the ssh channel behavior when the channel is terminated see ssh_channel(3erl) and should normally not be called explicitly. exec(ConnectionRef, ChannelId, Command, TimeOut) -> ssh_request_status() Types ConnectionRef = ssh_connection_ref() ChannelId = ssh_channel_id() Command = string() Timeout = timeout() Will request that the server start the execution of the given command, the result will be received as: N X {ssh_cm, ssh_connection_ref(), {data, ssh_channel_id(), ssh_data_type_code(), binary() = Data}} : The result of executing the command may be only one line or thousands of lines depending on the command. 1 X {ssh_cm, ssh_connection_ref(), {eof, ssh_channel_id()}} : Indicates that no more data will be sent. 0 or 1 X {ssh_cm, ssh_connection_ref(), {exit_signal, ssh_channel_id(), string() = ExitSignal, string() = ErrorMsg, string() = LanguageString}} : Not all systems send signals. For details on valid string values see RFC 4254 section 6.10 0 or 1 X {ssh_cm, ssh_connection_ref(), {exit_status, ssh_channel_id(), integer() = ExitStatus}} : It is recommended by the ssh connection protocol that this message shall be sent, but that may not always be the case. 1 X {ssh_cm, ssh_connection_ref(), {closed, ssh_channel_id()}} : Indicates that the ssh channel started for the execution of the command has now been shutdown. These message should be handled by the client. The ssh channel behavior can be used when writing a client. exit_status(ConnectionRef, ChannelId, Status) -> ok Types ConnectionRef = ssh_connection_ref() ChannelId = ssh_channel_id() Status = integer() Sends the exit status of a command to the client. reply_request(ConnectionRef, WantReply, Status, CannelId) -> ok Types ConnectionRef = ssh_connection_ref() WantReply = boolean() Status = ssh_request_status() ChannelId = ssh_channel_id() Sends status replies to requests where the requester has stated that they want a status report e.i . WantReply = true , if WantReply is false calling this function will be a "noop". Should be called after handling an ssh connection protocol message containing a WantReply boolean value. See the ssh_channel behavior callback handle_ssh_msg/2 send(ConnectionRef, ChannelId, Data) -> send(ConnectionRef, ChannelId, Data, Timeout) -> send(ConnectionRef, ChannelId, Type, Data) -> send(ConnectionRef, ChannelId, Type, Data, TimeOut) -> ok | {error, timeout} Types ConnectionRef = ssh_connection_ref() ChannelId = ssh_channel_id() Data = binary() Type = ssh_data_type_code() Timeout = timeout() Sends channel data. send_eof(ConnectionRef, ChannelId) -> ok Types ConnectionRef = ssh_connection_ref() ChannelId = ssh_channel_id() Sends eof on the channel ChannelId . session_channel(ConnectionRef, Timeout) -> session_channel(ConnectionRef, InitialWindowSize, MaxPacketSize, Timeout) -> {ok, ssh_channel_id()} | {error, Reason} Types ConnectionRef = ssh_connection_ref() InitialWindowSize = integer() MaxPacketSize = integer() Timeout = timeout() Reason = term() Opens a channel for a ssh session. A session is a remote execution of a program. The program may be a shell, an application, a sys- tem command, or some built-in subsystem. setenv(ConnectionRef, ChannelId, Var, Value, TimeOut) -> ssh_request_status() Types ConnectionRef = ssh_connection_ref() ChannelId = ssh_channel_id() Var = string() Value = string() Timeout = timeout() Environment variables may be passed to the shell/command to be started later. shell(ConnectionRef, ChannelId) -> ssh_request_status() Types ConnectionRef = ssh_connection_ref() ChannelId = ssh_channel_id() Will request that the user's default shell (typically defined in /etc/passwd in UNIX systems) be started at the other end. subsystem(ConnectionRef, ChannelId, Subsystem, Timeout) -> ssh_request_status() Types ConnectionRef = ssh_connection_ref() ChannelId = ssh_channel_id() Subsystem = string() Timeout = timeout() Sends a request to execute a predefined subsystem. Ericsson AB ssh 2.0.4 ssh_connection(3erl)
All times are GMT -4. The time now is 10:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy