Thanks for the reply and the questions!
I get the error when connected directly to the serial port and when connected connected to the network management port over the internal network via ssh.
If I try to connect via the remote console web gui however, I get an error message saying :
My OS is SunOS 5.10 Generic_144501-19 i86pc i386 i86pc
The server is an x4270_M2.
Hi folks. None of the conventional methods are working for my dilemma:
I have a file in my root directory that has a name comprised of strange characters. When I do an ls, it just hangs at that file until I do a Cntrl-C.
rm ./filename
&
rm \filename
do not work. I am entering the... (4 Replies)
Dear All:
I Have a bunch of files which I'd like to process with a shell script. The problem is that the files have strange characters in their headers, like
�g�8@L-000-MSG2__-ABCD________-FIRA_____-000001___-200806181330-__
��e�
Data from BLABLABLA, Instrument: BLABLA, Date:... (4 Replies)
I 've 2 different T5220 and both are showing different prompts when i ssh to the console.
1. Shows sc> ALOM
2. Shows -> ILOM
as far as i know the T5220 comes with ILOM , so why i 'm seeing 2 different type of console for same tyep of hardware ?
and i found that we... (6 Replies)
Hello all,
I'm new to UNIX and new to this forum, so forgive my lack of knowledge. I'm new with editing in vi so I FTP scripts to a Windows machine and edit the script in notepad (when I need to do something quickly). Sometimes when I FTP the script back to the UNIX box, strange characters... (4 Replies)
Hi,
I am just confused with iLOM. Is iLOM is applicable for SPARC as well as X86 servers?? which are having CMM. Hope ALOM will be applicable for rest of the servers like v240 kind of series.
Can any one pls clarify this??
Thanks in Advance
Vaisakh K S (3 Replies)
I've written a script:
find -depth | awk ‘
{
if ( substr($1,length($0)-2,3) == “/1.” )
{ print $1 }
{ system(“awk -f test1.awk “ $1 ) }
}
‘
The idea is that it trundles through a large directory structure looking for files which are named '1.' and then... (3 Replies)
Hello unix users :)
I am trying to grep a string from a file that both the file and the string may have characters in them that are quite... strange, like würzburger.
Well, bash reads this as
W%C3%BCrzburger
For example, if i do
wget W%C3%BCrzburger
the output is:
--2012-01-08... (2 Replies)
Hi guys,
After compiling a .f90 code and executing it, i get strange characters in the output file like :
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
Are these windows characters? how can i get rid of this?
Much appreciated.
Paul (1 Reply)
Dear all
would you tell me the command in ILOM to :
- Check for error logged in ILOM ouput
- Check for system uptime (DAYS)
- Check for system reboot logged (Last system reboot)
Thank you (1 Reply)
Discussion started by: gema.utama
1 Replies
LEARN ABOUT MOJAVE
udp
UDP(4) BSD Kernel Interfaces Manual UDP(4)NAME
udp -- Internet User Datagram Protocol
SYNOPSIS
#include <sys/socket.h>
#include <netinet/in.h>
int
socket(AF_INET, SOCK_DGRAM, 0);
DESCRIPTION
UDP is a simple, unreliable datagram protocol which is used to support the SOCK_DGRAM abstraction for the Internet protocol family. UDP
sockets are connectionless, and are normally used with the sendto and recvfrom calls, though the connect(2) or connectx(2) call may also be
used to fix the destination for future packets (in which case the recv(2) or read(2) and send(2) or write(2) system calls may be used).
UDP address formats are identical to those used by TCP. In particular UDP provides a port identifier in addition to the normal Internet
address format. Note that the UDP port space is separate from the TCP port space (i.e. a UDP port may not be ``connected'' to a TCP port).
In addition broadcast packets may be sent (assuming the underlying network supports this) by using a reserved ``broadcast address''; this
address is network interface dependent.
Options at the IP transport level may be used with UDP; see ip(4).
DIAGNOSTICS
A socket operation may fail with one of the following errors returned:
[EISCONN] when trying to establish a connection on a socket which already has one, or when trying to send a datagram with the destina-
tion address specified and the socket is already connected;
[ENOTCONN] when trying to send a datagram, but no destination address is specified, and the socket hasn't been connected;
[ENOBUFS] when the system runs out of memory for an internal data structure;
[EADDRINUSE] when an attempt is made to create a socket with a port which has already been allocated;
[EADDRNOTAVAIL] when an attempt is made to create a socket with a network address for which no network interface exists.
SEE ALSO connect(2), connectx(2), getsockopt(2), recv(2), send(2), socket(2), inet(4), intro(4), ip(4)HISTORY
The udp protocol appeared in 4.2BSD.
4.2 Berkeley Distribution March 18, 2015 4.2 Berkeley Distribution