search for: ssing

...e with changing expired passwords through SSH connection. We always have to tell our users to use telnet to change the password. We want to completely shutdown telnet on all of our systems, because of this issue we are not able to shut it down. Is there a known issue with OpenSSH, or am I just missing some configuration. Thanks in advance for your help. -Sandeep

...tant_name ''", "C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/active_support/dependencies.rb:214:in `qualified_nam e_for''", "C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/active_support/dependencies.rb:476:in `const_mi ssing''", "C:/InstantRails/ruby/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/dispatcher.rb:117:in `reset_after_dispatch''", "C:/Insta ntRails/ruby/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/dispatcher.rb:51:in `dispatch''", "C:/InstantRails/ruby/lib/ruby/gems/1...

...4:10.0.0.28:57631) SMB3_11 - - 17739 nobody nobody 10.0.0.28 (ipv4:10.0.0.28:57631) SMB3_11 - - 17739 nobody nobody 10.0.0.28 (ipv4:10.0.0.28:57631) SMB3_11 - And repeat to infinity. The smbd.log log: Ssing section "[Reception]" [2017/04/21 00: 34: 52.460998, 2] ../source3/param/loadparm.c:2688(lp_do_section) Processing section "[Systems]" [2017/04/21 00: 34: 52.461107, 2] ../source3/param/loadparm.c:2688(lp_do_section) Processing section "[files]" [2017/04/21 00: 34:...

Hi, Is there a recommended way to get and monitor the MDB state from userspace, without potential synchronization races? I can use "bridge monitor mdb" to get changes or "bridge mdb show" to get the current state (as well as use the underlying netlink calls from my own application without the "bridge" command). But if I were first calling "bridge mdb

Hi, I'm trying to get Asterisk running with LDAP to be able to authenticate sip user registrations. I'm using Asterisk (1.8.13.1~dfsg1-3+deb7u3) on a Debian server. Unfortunately I wasn't successful so far. My res_ldap.conf looks like this (so pretty minimal): --- [_general] ;url=ldaps://ldap.chaotikum.org url=ldap://ldap.chaotikum.org protocol=3 basedn=dc=chaotikum,dc=org [sip]

...nobody 10.0.0.28 (ipv4:10.0.0.28:57631) SMB3_11 - - >> 17739 nobody nobody 10.0.0.28 (ipv4:10.0.0.28:57631) SMB3_11 - >> >> And repeat to infinity. >> >> The smbd.log log: >> >> Ssing section "[Reception]" >> [2017/04/21 00: 34: 52.460998, 2] ../source3/param/loadparm.c:2688(lp_do_section) >> Processing section "[Systems]" >> [2017/04/21 00: 34: 52.461107, 2] ../source3/param/loadparm.c:2688(lp_do_section) >> Processing section &qu...

I believe I have found the cause of the unexplained error (code ??) at main.c(line #). In the version I'm running 2.5.2 (obtained from the Free Software Foundation) the line number is 576. It appears the root cause is related to a race condition associated with the termination of child processes. If the signal handler for SIGCHILD is executed, as the result of a child termination, before the

...- > 17739 nobody nobody 10.0.0.28 (ipv4:10.0.0.28:57631) SMB3_11 - - > 17739 nobody nobody 10.0.0.28 (ipv4:10.0.0.28:57631) SMB3_11 - > > And repeat to infinity. > > The smbd.log log: > > Ssing section "[Reception]" > [2017/04/21 00: 34: 52.460998, 2] ../source3/param/loadparm.c:2688(lp_do_section) > Processing section "[Systems]" > [2017/04/21 00: 34: 52.461107, 2] ../source3/param/loadparm.c:2688(lp_do_section) > Processing section "[files]"...

...pv4:10.0.0.28:57631) SMB3_11 - - >>> 17739 nobody nobody 10.0.0.28 (ipv4:10.0.0.28:57631) SMB3_11 - >>> >>> And repeat to infinity. >>> >>> The smbd.log log: >>> >>> Ssing section "[Reception]" >>> [2017/04/21 00: 34: 52.460998, 2] ../source3/param/loadparm.c:2688(lp_do_section) >>> Processing section "[Systems]" >>> [2017/04/21 00: 34: 52.461107, 2] ../source3/param/loadparm.c:2688(lp_do_section) >>> Proces...

...hat these phones do NOT have the ability to handle a 2nd= ringing call. So in the event that 2 inbound calls rang within a few secon= ds, asterisk would send the first to all phones, and then when tyring to se= nd the 2nd, would receive a BUSY message from the phones (because they were= busy processing a ring for the first caller), and the 2nd caller would win= d up going straight to the unavilable destination for the ring group, inste= ad of eventually ringing through to the phones after someone answered the f= irst call. I greatly appreciate your help & insight with this issue! - Doug Mort...

Processing commands for control at bugs.debian.org: > submitter 192827 Jos? Luis Gonz?lez <jlgonzal at ya.com> Bug #192827 [xdiskusage] xdiskusage: Printing doesn't manage non-ASCII characters Changed Bug submitter to 'Jos? Luis Gonz?lez <jlgonzal at ya.com>' from 'Jos?? Luis G...