similar to: Bug Report - sshd invoked by inetd (follow-up)

Displaying 20 results from an estimated 5000 matches similar to: "Bug Report - sshd invoked by inetd (follow-up)"

2000 Nov 09
0
Bug Report - sshd invoked by inetd on Solaris 8
Hello, My apologies if this is a known "feature" and I'm simply reporting something already known. The situation is this: - the sshd in openssh-2.3.0p1 (and also previously in openssh-2.1.1p4) fail when invoked via inetd on Solaris 8 - the sshd is invoked with: 1) an entry in /etc/services: sshback 10000/tcp sshdback # SSH Back Door 2) an entry
2012 Jan 30
0
[Bug 36090] terminal's visual bell is very slow with nouveau
https://bugs.freedesktop.org/show_bug.cgi?id=36090 aebenjam at opentext.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aebenjam at opentext.com --- Comment #1 from aebenjam at opentext.com 2012-01-30 08:34:15 PST --- Also experienced with: 01:00.0
2013 Sep 23
0
[Bug 36090] [NV34] [NV49] terminal's visual bell is very slow with nouveau
https://bugs.freedesktop.org/show_bug.cgi?id=36090 aebenjam at opentext.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #5 from aebenjam at opentext.com --- Problem still exists
2014 May 08
16
[Bug 78441] New: X does not start under kernel 3.13.x
https://bugs.freedesktop.org/show_bug.cgi?id=78441 Priority: medium Bug ID: 78441 Assignee: nouveau at lists.freedesktop.org Summary: X does not start under kernel 3.13.x QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: aebenjam at opentext.com
2007 Jul 21
5
[Bug 1344] New: DISABLE_FD_PASSING does not work if sshd invoked by inetd
http://bugzilla.mindrot.org/show_bug.cgi?id=1344 Summary: DISABLE_FD_PASSING does not work if sshd invoked by inetd Product: Portable OpenSSH Version: 4.6p1 Platform: Other OS/Version: Other Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: bitbucket at
2013 Sep 23
0
[Bug 36090] [NV34] [NV49] terminal's visual bell is very slow with nouveau
https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #7 from aebenjam at opentext.com --- I'm not sure how to answer your question about the ddx... is this what you mean? rpm -qa |grep -i nouveau xorg-x11-drv-nouveau-1.0.7-1.fc18.i686 Re: the card, dmidecode suggests it is: Quadro NVS 110M Let me know if you need more. Thanks, Adam -- You are receiving this mail because: You
2013 Sep 23
0
[Bug 36090] [NV34] [NV49] terminal's visual bell is very slow with nouveau
https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #9 from aebenjam at opentext.com --- #dmesg | grep -i chipset [ 1.887251] nouveau [ DEVICE][0000:01:00.0] Chipset: G72 (NV46) Reproduction: You can fire up an xterm with -vb to request the visual bell. You can also use control + middle-mouse-button to bring up a menu which allows you to enable/disable the visual bell. Let me
2013 Sep 24
0
[Bug 36090] [NV34] [NV49] terminal's visual bell is very slow with nouveau
https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #11 from aebenjam at opentext.com --- Interesting. So, I'm a Fedora (currently v18) user. I created a stock account, logged in to a standard Gnome environment, and fired up an xterm with visual bell running, and it doesn't have the same problem. In fact, I couldn't even SEE a visual bell. Odd. All I could tell was that
1998 Oct 01
1
inetd and Solaris
Environment: Solaris 2.5.1 Samba 1.9.18p3 We run samba from inetd (no special reason - just how its been done in the past). Then on one server we got masses of Samba daemons running (up to 40 as a time trying to run - load average 40+!), giving following complaints: Sep 28 14:39:06 zeus.brunel.ac.uk smbd[10728]: standard input is not a socket, a ssuming -D option Sep 28 14:39:06
2014 Jan 30
0
Issue with running tftpd-hpa in inetd mode?
On Thu, 2014-01-30 at 11:25 -0500, Dan Swartzendruber wrote: > Hopefully I'm not out to lunch here. I ported tftp-hpa to our proprietary > OS, VOS (at stratus.com). We've always runs the old legacy tftpd from > inetd, so I wanted to continue doing so with tftp-hpa. It seems to work > okay, but I noticed that the code in tftpd.c has a 'while (1)' loop that > has
1997 Jul 30
0
Can't run SAMBA from inetd
I'm trying to start SAMBA from the inetd. I have added the port numbers to /etc/services: netbios-ns 137/udp netbios-ssn 139/tcp To my inetd.conf I have added: netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd After this I killed any samba-prosecces, and refreshed the inetd with:
2001 Apr 04
0
help me samba [inetd]
> ?????? wrote: > > Hello Sir/Madam! > > my name is dae su kim! > i have a problem diffcult! > The problem is samba process smbd and nmbd no responsing! > This log is my problem! > help me! please help me! > > problem : SAMBA_2.0.7 > > 7 03:13:48 cad1 inetd[179]: netbios-ns/udp server > failing > 7 03:27:03 cad1
2014 Jan 30
2
Issue with running tftpd-hpa in inetd mode?
> Correct. Like most UDP-based inetd services, tftpd is intended to be run in 'wait' mode. When the first request arrives, inetd starts the service but does not read the incoming packet (it can't, because it has no way to pass it along to the server). After that, inetd ignores that socket until the server exits. This isn't critical for tftp, but it does help to keep down the
2014 Jan 30
1
Issue with running tftpd-hpa in inetd mode?
On 01/30/2014 10:25 AM, Jeffrey Hutzelman wrote: > > Correct. Like most UDP-based inetd services, tftpd is intended to be > run in 'wait' mode. When the first request arrives, inetd starts the > service but does not read the incoming packet (it can't, because it has > no way to pass it along to the server). After that, inetd ignores that > socket until the server
2004 Sep 10
4
question about using rsync with inetd
Hello, we would like to use rsync (2.6.2 manualy patched and recompiled) in daemon mode spawned by inetd (Solaris 5.8 Environment). /etc/services: rsync 1234/tcp #RSYNC daemon /etc/inet/inetd.conf: rsync stream tcp nowait publish /usr/bin/rsync rsyncd --daemon --port 1234 . Alas, this does not seem to work, there is the following error message in the log file:
2013 Sep 16
1
Upgrading samba 2.2.8a to 3.6.15 on Solaris 9 --> 3.6.15 brings all inetd services down
Hi samba friends, I'm upgrading our Samba 2.2.8a server to 3.6.15 on a Solaris 9 box, we need to do this as all our latest Mac OS X 10.8 clients cannot map to the 2.2.8a network share, and need the newer Samba (well known issue for mountain lion). I've compiled 3.6.15 and this seemed to go ok, no obvious errors were shown during .configure make and make install, and smbd -V gives
2004 Jan 09
2
inetd & etc
Hello. I know that it is recommended to run smbd as a standalone daemon and to avoid inetd. Can you please tell me why inetd is discouraged and what problems it imposes? Also, I have one user who is having problems accessing her personal files on a MacOSX 10.3.2 via smb. Any ideas what may be causing it? Judy Lin NACS-DCS
2011 Mar 17
1
inetd config - dovecot doesn't exits
Is there any option for dovecot to exit when is unneded? I mostly use dovecot via shell process (ie. something like /usr/sbin/dovecot --exec-mail imap) But sometimes I want to use it remotely via tcp and I run dovecot via inetd. --8<---------------cut here---------------start------------->8--- localhost:imap stream tcp nowait root /usr/sbin/tcpd
2001 Feb 15
0
Mandrake and xinetd/inetd issues
I was searching for help on Mandrake's site and got nowhere other than seeing this really weird help-page loop where it showed the pages you could go to, BUT would not show any information from the page.... Just use the search from www.mandrake.com to see this strangeness.... No helpful... Anyway.. trying to run drakconf and startup services to start either inetd or xinetd seems to be
2009 Jan 28
0
Solaris removing ktkt_warnd from inetd.conf
Have a system admin who would like to stop running inetd on his Solaris 9 system. Currently the only thing left in his /etc/inet/inetd.conf file is: 100134/1 tli rpc/ticotsord wait root /usr/lib/krb5/ktkt_warnd ktkt_warnd Does anyone know if they can remove this without causing any problems?