02-02-2016
Thank you for the reply bakunin. I apologize for not writing back sooner. During the time between replies I actually gave up and installed Bunsen Labs distro and Kali's tools on it instead. Lately I've had problems getting anyone to comment on my threads Such as this thread from August that never got a reply:
https://www.unix.com/unix-for-dummies...onfigured.html
Its no biggie, I just get complacent when I get accustomed to waiting that long. Thank you for trying though. I will keep this in mind if I run into it again.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
After installing an internal fax modem I get the message above when using the cu -l /dev/tty1A command.
Any help would be most appreciated to the cu command to work again. Thanks. (3 Replies)
Discussion started by: cfaiman
3 Replies
2. Programming
Hello All,
I have a problem using connect(...) function in C++. I am using SSH from my windows system to connect it to linux server. The program works fine if I run it directly in Linux machine but I need it to run through windows machine.
The function returns -1 and so my program terminates.
... (3 Replies)
Discussion started by: smdhd3
3 Replies
3. UNIX for Advanced & Expert Users
Hi,
I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime.
To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Discussion started by: chandrutiptur
0 Replies
4. Programming
Is there any relation between the connect() socket API and the TCP's Transmission Control Block.
Also how does connect detect that a socket is in use i.e., EADDRINUSE (1 Reply)
Discussion started by: sunaina
1 Replies
5. Solaris
Dear All,
I have server with SunOS 5.10 Generic_127111-06 sun4v sparc SUNW,SPARC-Enterprise-T5120, always coming out error message like this :
May 25 10:37:26 sshd: fatal: Read from socket failed: Connection reset by peer
So what happend with my server..???
Best Regards
Bejo :D (2 Replies)
Discussion started by: mbah_jiman
2 Replies
6. UNIX for Dummies Questions & Answers
I get this error when I log in through console:
"fatal: Read from socket failed: Connection reset by peer".
Can you tell me what this is and why it happens, and how to stop it? Thank you. (1 Reply)
Discussion started by: iamnew2solaris
1 Replies
7. UNIX for Dummies Questions & Answers
solaris client report "cannot to socket(code 25)" while trying to backup on veritas netbackup 6.5.5 server (1 Reply)
Discussion started by: EUGINIAM
1 Replies
8. Programming
will there be any unexpected results on looping connect call for a non blocking socket to determine the connection based on error code. I am getting connection unsuccessful intermittently and so wondering whether is the timeout 500 millisec not sufficient or looping connect cause any unexpected.
... (7 Replies)
Discussion started by: satish@123
7 Replies
9. UNIX for Advanced & Expert Users
Hello,
I have recently updated my AIX machine from version 6.1.7.5 to 6.1.9.1 and i noticed that the errpt of the server is full of ssh messages like the one below:
sshdprocess_id>]: fatal: Read from socket failed: Connection reset by peer
Does anyone knows if this a known bug of the ssh... (15 Replies)
Discussion started by: omonoiatis9
15 Replies
LEARN ABOUT LINUX
dbus-cleanup-sockets
dbus-cleanup-sockets(1) General Commands Manual dbus-cleanup-sockets(1)
NAME
dbus-cleanup-sockets - clean up leftover sockets in a directory
SYNOPSIS
dbus-cleanup-sockets [DIRECTORY]
DESCRIPTION
The dbus-cleanup-sockets command cleans up unused D-Bus connection sockets. See http://www.freedesktop.org/software/dbus/ for more informa-
tion about the big picture.
If given no arguments, dbus-cleanup-sockets cleans up sockets in the standard default socket directory for the per-user-login-session mes-
sage bus; this is usually /tmp. Optionally, you can pass a different directory on the command line.
On Linux, this program is essentially useless, because D-Bus defaults to using "abstract sockets" that exist only in memory and don't have
a corresponding file in /tmp.
On most other flavors of UNIX, it's possible for the socket files to leak when programs using D-Bus exit abnormally or without closing
their D-Bus connections. Thus, it might be interesting to run dbus-cleanup-sockets in a cron job to mop up any leaked sockets. Or you can
just ignore the leaked sockets, they aren't really hurting anything, other than cluttering the output of "ls /tmp"
AUTHOR
dbus-cleanup-sockets was adapted by Havoc Pennington from linc-cleanup-sockets written by Michael Meeks.
BUGS
Please send bug reports to the D-Bus mailing list or bug tracker, see http://www.freedesktop.org/software/dbus/
dbus-cleanup-sockets(1)