similar to: mail_always fails in CentOS 5

> Date: Tuesday, June 16, 2015 07:05:43 PM -0400 > From: Steve Matzura <number6 at noisynotes.com> > > On Tue, 16 Jun 2015 17:31:07 +0000, you wrote: > >> By default, most MTAs only listen to localhost, so don't accept >> externally derived mail. Try telnetting to port 25 on the machine >> from some place off your machine's network. If you get a

> Date: Tuesday, June 16, 2015 01:13:47 PM -0400 > From: Steve Matzura <number6 at noisynotes.com> > > On Tue, 16 Jun 2015 11:27:58 -0500, you wrote: > >> No attempt to deliver almost always means either: >> - a DNS problem; the sender can't find the destination, or finds >> the "wrong" destination. > > That would be interesting, since I

Using 1.6 on Fedora Core 9 I'm trying to receive faxes. I've got this far: [incoming-fax] exten => s,1,Set(FAXFILE=/var/spool/asterisk/fax/${STRFTIME(${EPOCH},,%Y%m%d%H%M)}-0${CALLERIDNUM}) exten => s,2,ReceiveFAX(${FAXFILE}.tif) exten => s,3,Hangup() exten=>h,1,System(/usr/local/bin/fax2mail --cid-number "0${CALLERIDNUM}" --cid-name "home fax"

Strange issue.... when I record a file from a phone to the asterisk system I get a blip in the recording every 30 seconds. It's a very small blip, but it is there. It seems like it's only if I'm recording, not when I'm playing back that the issue happens. My SATA drives, ETH0, and my Sangoma card are all on seperate IRQs. Any thoughts on what might be causing this and how to

Hi, I have an IVR that sounds just fine and dandy over ZAP. However, when I dial in through an 800 number from a provider that I connect to via IAX I get this 'blip' in the sound file. At first I thought it was just packet loss, but it happens at the exact same spot every single time. There are several parts to the IVR menu and several places where this blip happens every single time

Hi all! I'm attempting to configure sudo rights from Samba ldap. Alas, libsssd_samba receives 0 rules and config doesn't work. I think I have the problem identified here but I don't understand why. The way sssd_sudo searches for sudoers leave all important attributes out and of course filtering then fails. Can you help me to understand why following search results are so different (and

Hi, I'm having hard time getting sssd_sudo to work: when sssd_sudo accesses Samba ldap with host principal 'dc1$@teemu.local' it can't read necessary attributes like objectclass: sudoRole. When accessing as Administrator all attributes are shown. How can I enable other users then Administrator to access sudoers' attributes? Below is an example. [root at dc1 var]# kinit

I took your suggestion and turned my (ill advised) sudoers bash script into an expect script! It works a lot better this way and is more secure. Because I'm not trying to store a password in a script (which I recognize as a bad idea anyway, I I think I've learned my lesson here). It really works well. But the only thing I'm still trying to figure out is how to put a if statement in

Hello list, I took another stab at finding a way to add a sudo user remotely and it gets you most of the way there. If you execute the script as root it works beautifully and does just what you want. Which is add the user to the group and gives that user group rights to certain commands. But if you execute it as a user who only has sudo access to the /etc/sudoers file it errors out. cloud:~]

Nice Ribbit Demo http://blip.tv/file/753401 I think we should get some Asterisk video demo's up on blip.tv as well. Post to this list with the url once you have your demo's up there. Regards, Dean Collins Cognation Pty Ltd dean at cognation.net +1-212-203-4357 +61-2-9016-5642 (Sydney in-dial). -------------- next part -------------- An HTML attachment was scrubbed...

On Fri, 24 Nov 2023 13:30:13 +0500 Anton Shevtsov via samba <samba at lists.samba.org> wrote: > Hi, > > I have a DC on samba 4.17.12 > > I want store sudoers in LDAP, and use sssd for get rules from LDAP. > > I was configured sssd.conf > > [sssd] > config_file_version = 2 > services = nss, pam, sudo > user = _sssd > domains = TEST.ALT > >

Hi, I have a DC on samba 4.17.12 I want store sudoers in LDAP, and use sssd for get rules from LDAP. I was configured sssd.conf [sssd] config_file_version = 2 services = nss, pam, sudo user = _sssd domains = TEST.ALT [nss] [sudo] [pam] [domain/TEST.TLD] dyndns_update = true id_provider = ad auth_provider = ad chpass_provider = ad access_provider = ad default_shell = /bin/bash

Hello there, I have come to a situation where I would like to mix 2 approaches to create the contents of a file. Here is what I have: a module ''sudo'' which manages a hosts /etc/sudoers file: init.pp: class sudo { case $operatingsystem { Debian: { package { "sudo": } } } file { "/etc/sudoers": mode => 440, content =>

24.11.2023 14:57, Rowland Penny via samba ?????: > On Fri, 24 Nov 2023 13:30:13 +0500 > Anton Shevtsov via samba<samba at lists.samba.org> wrote: > >> Hi, >> >> I have a DC on samba 4.17.12 >> >> I want store sudoers in LDAP, and use sssd for get rules from LDAP. >> >> I was configured sssd.conf >> >> [sssd] >>

Hello CentOS I am having a bit of trouble importing an ldif into openldap, tho the syntax looks a-ok to me. I am attempting to import my sudoers list into my ldap configuration and I used an application called sudoers2ldif to generate the ldif. I used the following command to import the file: ============================================= [root at bluethundr-desktop:~/txt/ldif ] $:ldapadd -h

Today I was testing Puppet''s fileserver feature and and error came up: client> /usr/sbin/puppetd --test --verbose --server puppet info: Caching catalog at /var/lib/puppet/localconfig.yaml notice: Starting catalog run notice: //Node[default]/sudo/Package[sudo]/ensure: created err: //Node[default]/sudo/File[/etc/sudoers]: Failed to retrieve current state of resource: No specified source

Hey Gordon, Sorry, man my bad! Disabling the tty requirement for my sudo user does indeed work. I had a type-o in the sudoers file, and when I corrected it, my sudo command via pssh started working! #pssh -i -h es_list "/bin/sudo /bin/systemctl restart elasticsearch; sleep 10" [1] 20:31:32 [SUCCESS] bluethundr at es3.jokefire.com Stderr: sudo: sorry, you must have a tty to run sudo

On 2/20/2014 6:55 AM, Charles Lepple wrote: > On Feb 19, 2014, at 12:50 PM, Ted Mittelstaedt wrote: > >> Worse, however, is if there's a power failure right near the end of >> the 2-days-off cycle. That happened to me last week - it was a >> short duration 15 second loss - and the upscode2 driver decided it >> needed to issue a forced shutdown. >> >>

so I have this sudo module that I''ve been working on: class auth::sudo { package { sudo: ensure => installed } file { sudo_config: name => "/tmp/sudoers", owner => "root", group => "root", mode => 0440, notify => Exec["sudoers-syntax"], source => [

ok after fighting to get my groups sorted out for my test user I created an "sudoer" group and added "jefftest" to "sudoer" > id jefftest uid=11507(jefftest) gid=8513(domain users) groups=8513(domain users),31020(sudoer) and added "sudoer" to /etc/sudoers like so %sudoer ALL=(ALL) ALL now when I login as jefftest I can run commands using sudo back to