Displaying 20 results from an estimated 100000 matches similar to: "NETWORK SOCKET!!!"
2007 Jan 22
2
local IP address for NETWORK SOCKET
How wine define local IP settings for creating socket?
does it use tcp/ip API of Linux kernel?
have a problem with few networking application. It is able to use simple
queries if it is forks just as client for example Internet browser, but
if it trying to create socket it listen port on a wrong IP address or
just does not create socket....
also in .wine directory I find file .wine/igsp.log which
2006 Dec 27
1
network application problem
Installed BuddyTalk Dialer (VoIP client). It was requested mfc42.dll
which I was download and put in system32. After running it could not
regiter with server. Probably because it is incorrectly create udp
socket. it listen UDP port 8481 on 255.255.255.255 address instead of
0.0.0.0 which linux kernel usually listen. I use kernel 2.6.17-10-386
Ubuntu edgy 6.10
here a netstat output
winehost:~$
2016 Jul 07
1
Icecast is running, but not responding
Howdy,
I work for a public radio station, and have setup several Icecast servers
in the past to stream our content. We have a new HD channel that we are
trying to stream, and the new server is vexing me.
This is a fresh dedicated server running RHEL 7.2 on a virtual system
running VMWare 6.1.
The install was done with the command yum --nogpgcheck localinstall
icecast-2.4.2-1.el7.x86_64.rpm
I
2024 May 30
2
[Bug 3695] New: X11 forwarding via UNIX socket instead of 127.0.0.1
https://bugzilla.mindrot.org/show_bug.cgi?id=3695
Bug ID: 3695
Summary: X11 forwarding via UNIX socket instead of 127.0.0.1
Product: Portable OpenSSH
Version: 9.7p1
Hardware: Other
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: ssh
Assignee:
2011 Jun 02
2
Restarting a Perl-script (socket daemon) from /etc/inittab
Hello fellow CentOS sysadmins,
I run a small multiplayer card game
with around 500 users at peak times.
The client is in Flash and the server is in Perl.
The Perl server binds to port 8080, i.e. only
1 instance of it can be started (important detail).
The Perl server poll()s TCP-sockets and forks
only once - at the startup by calling this method:
sub daemonize {
die "Can not
2007 Jun 14
1
using 'socat' to relay Dovecot SASL's auth socket over TCP?
hi,
i've been running Exim & Dovecot together on the same box.
Exim's been sharing Dovecot/SASL auth info over a local unix socket.
works great.
i'm now splitting Exim & Dovecot onto two different boxes.
iiuc, Dovecot ONLY provides a UNIX (local) socket; *not* a TCP socket
for over-the-network access. SUre, I could mount the Dovecot socket's
volume over NFS ... but
2007 Apr 11
1
bind or samba configuration preventing browsing network
I have a networking problem where I am not certain if the problem is
samba or bind. I am still pretty much a nb at linux. The machine in
question is running openSuSE 10.2 and is named rd1. I had samba working
fine before I started to make it a WINS server and DNS host.
I have a small LAN with no real administration functionality. The
network is used for simple file sharing and dial-up
2003 Sep 22
1
smbclient 127.0.0.1 timeout .... PCs can't browse LInux share
Let's see I've got a network about 10 PCs running XP and 1 running
Linux. I had setup Samba and it was running like a charm. XP pcs
could access linux box through network neighborhood and access 2
shared dir and edit/change files.
Really not sure what has gone wrong. I am using Samba 2.2.8a
I run both smbd and nmbd as daemons. When I run ps -aux they show up.
root 1553 0.0
2013 Dec 11
2
[Bug 2183] New: ssh -g has no effect if master socket already open
https://bugzilla.mindrot.org/show_bug.cgi?id=2183
Bug ID: 2183
Summary: ssh -g has no effect if master socket already open
Product: Portable OpenSSH
Version: 6.4p1
Hardware: amd64
OS: Linux
Status: NEW
Severity: minor
Priority: P5
Component: ssh
Assignee: unassigned-bugs at
2007 Jan 04
1
samba needed to network across openvpn tunnel
I have been assued in other places that I need to have Samba and Wins
in place touse Windows networking across an openvpn tunnel.
back history:
There was a network in place when I was hired to replace the former it
guy. All ran very smooth with only one networking issue. There were
"fights" between the Windows server and the Linux box:
The master browser has received a server
2013 Oct 17
0
ANNOUNCE: CVE-2013-4419: insecure temporary directory handling for guestfish's network socket
This issue has been assigned CVE-2013-4419.
https://bugzilla.redhat.com/show_bug.cgi?id=1016960
(Note this bug is private, but will be made public shortly)
----------------------------------------------------------------------
When using the guestfish --remote or guestfish --listen options,
guestfish would create a socket in a known location
(/tmp/.guestfish-$UID/socket-$PID).
The location has
2020 Oct 25
0
Socket is busy: Success?
Is your icecast server in another server?
If not, if you are running ices on the same server as your icecast, try
using localhost instead of "bananradion.bananklubben.se"
Cheers,
--
Kwame
On Sun, Oct 25, 2020 at 11:44 AM Bananradion <bananradion at gmail.com> wrote:
> tcp 0 0 0.0.0.0:8443 0.0.0.0:*
> LISTEN 8421/icecast2
> tcp 0
2020 Oct 25
0
Socket is busy: Success?
I changed to "localhost" in the ices-config and got this error:
EROR stream/ices_instance_stream Failed initial connect to localhost:8443
(TLS connection can not be established because of bad certificate: Success)
/Daniel
Den sön 25 okt. 2020 kl 19:00 skrev Bananradion <bananradion at gmail.com>:
> Both icecast and ices are on the same server.
> Where shall i change to
2023 Mar 23
1
[libnbd PATCH v3 07/19] socket activation: replace execvp() call with fork-safe variant
Per POSIX, execvp() is not safe to call in a child process forked from a
multi-threaded process. We can now replace the execvp() call in the child
process with a call to our fork-safe (async-signal-safe) variant.
Prepare our internal execvpe context on the parent's construction path,
use the context in the child, and release the context in the parent on the
way out, regardless of whether the
2020 Oct 25
2
Socket is busy: Success?
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN
8421/icecast2
tcp 0 0 192.168.1.159:8443 192.168.1.1:65003
ESTABLISHED 8421/icecast2
Den sön 25 okt. 2020 kl 18:42 skrev Kwame Bahena <informatux at gmail.com>:
> Hello,
>
> What does the command
>
> sudo netstat -plant | grep 8443
>
> say?
>
> Cheers,
> --
>
2020 Oct 25
2
Socket is busy: Success?
Both icecast and ices are on the same server.
Where shall i change to "localhost"?
/Daniel
Den sön 25 okt. 2020 kl 18:49 skrev Kwame Bahena <informatux at gmail.com>:
> Is your icecast server in another server?
> If not, if you are running ices on the same server as your icecast, try
> using localhost instead of "bananradion.bananklubben.se"
>
>
>
2002 Mar 18
0
[Bug 173] New: sshd does not listen on tcp-socket, though GatewayPorts yes
http://bugzilla.mindrot.org/show_bug.cgi?id=173
Summary: sshd does not listen on tcp-socket, though GatewayPorts
yes
Product: Portable OpenSSH
Version: 3.1p1
Platform: UltraSparc
OS/Version: SunOS
Status: NEW
Severity: normal
Priority: P2
Component: sshd
AssignedTo:
2023 Oct 17
1
"Could not create listener socket on port" error only when using systemd service
V?Mon, Oct 16, 2023 at 12:34:42PM -0700,?Jordan Erickson napsal(a):
> On 10/16/23 10:37, Michael C Cambria wrote:
> > I'm using icecast via Fedora 37 package and systemd service to start.
> >
> > I've added multiple <listen-socket> but get:
> >
> > "EROR connection/connection_setup_sockets Could not create listener
> > socket on port
2011 Aug 18
4
[RFC 0/0] Introducing a generic socket offload framework
TL;DR
-----
In this RFC we propose the introduction of the concept of hardware socket
offload to the Linux kernel. Patches will accompany this RFC in a few days,
but we felt we had enough on the design to solicit constructive discussion
from the community at-large.
BACKGROUND
----------
Many applications within enterprise organizations suitable for virtualization
neither require nor desire a
2011 Aug 18
4
[RFC 0/0] Introducing a generic socket offload framework
TL;DR
-----
In this RFC we propose the introduction of the concept of hardware socket
offload to the Linux kernel. Patches will accompany this RFC in a few days,
but we felt we had enough on the design to solicit constructive discussion
from the community at-large.
BACKGROUND
----------
Many applications within enterprise organizations suitable for virtualization
neither require nor desire a