similar to: upgrade 3.04 to 3.0.23d ?

Hi, I'm trying to compile samba 3.0.23d for use with ldap as backend. The system is Debian Sarge fresh installed, all updates installed, and openldap-2.3.27 installed from sources. I searched a lot but couldn't google out anythink that helped. I sent this same mail jesterday with configure options for ldap, ld.so.conf and samba error.log but it was too long. So another time with less

I'm new to Kerberos. I don't understand how Samba uses the system keytab (/etc/krb5.keytab) when "use kerberos keytab = true". Does Samba use service specific tickets? What tickets does Samba add? Do I need a cron job to keep them fresh or does Winbind take care of it? Sorry if these are elementary questions, but the Samba HOWTO didn't help me understand Samba's

Whenever I try to read or modify ACLs from my Windows 2000 PDC, my Samba Domain Member Server (Security = ADS) does not allow setting ACLs, nor does it display the existing ACLs. - I have setup ACLs in my Kernel - I have translated and installed libacl and libattr - I can see and modify ACLs with getfacl and setfacl. - I have translated Samba 3.0.23d with --with-acl-support=yes - I have enabled

I think the message title says it all. I was attempting to do 'make test' against 3.0.23d and include the smbtorture4 tests from 4.0.0tp3 (as I read somewhere to be a good idea). Is there any reason that the test should not work? Does it have something to do with the 'unknown parameter'? Make test works fine without smbtorture4. Platform is Solaris 9 on sun4u. Samba 4 was

I posted this to the amanda-users ml earlier today, as I run several amanda backup servers and hit this issue again today. -> "I have to upgrade to samba-4.2.11 (gentoo linux) on an amanda server running amanda-3.4.1 Does anyone know if this: http://www.backupcentral.com/forum/16/263253 ... is still an issue?" -| my interpretation: samba-4.2.11 / smbclient has problems with

I am trying to configure a samba with openldap as a PDC on SuSE9.1 with samba-3.0.4, openldap2-2.2.6, samba-winbind-3.0.4, following the book Samba-3 By Example, by John H. Terpstra. I am getting errors "NT_STATUS_LOGON_FAILURE" from smbclient commands and "The username or password was not correct." from 'net' commands. Anonymous smbclient access seems to work, and I

Hi Robert - I'm running it successfully on C7 using xinetd.? Do you have documentation for running it directly from systemd?? Working xinetd configuration: cat /etc/xinetd.d/amanda # default: off # description:? The client for the Amanda backup system.\ #?????????????? This must be on for systems being backed up\ #?????????????? by Amanda. service amanda { ??? disable???????? = no ???

hello puppet list My puppet server is now working quite wonderfully. Thanks go out to all who have assisted in getting it to this point. At this point in time my config is now correctly installing packages according to arch,os and release. Centos is working quite well as of now, but I am attempting to get the ubuntu side of things to work as well. I am frankly more familiar with RHEL under

I am trying to get amanda backup going on a CentOS 7 system and things are not working: sharky4.deepsoft.com% sudo systemctl start amanda-udp [sudo] password for heller: Job for amanda-udp.service failed because a configured resource limit was exceeded. See "systemctl status amanda-udp.service" and "journalctl -xe" for details. sharky4.deepsoft.com% sudo systemctl status -l

I''ve been working up my first puppet module, one that will make Amanda configurations consistently. In general, I''d like the following to happen: - Each Amanda server should make sure all its holding disks are configured properly; this should only happen once per server, per puppetd run. Definitely not on a per-configuration basis. - Each Amanda server should keep its

I am running a Debian Linux system with Samba 3.0.23d and the 2.6.8-3-386 kernel. I found a howto for adding a debian samba server to an ADS domain on debian-administrator.org but when I get to the point of actually running the 'net ads join' I get the following errors: 'resolve_name:unknown name switch type dns' And 'ads_connect:No such file or directory' Does anyone

CentOS Errata and Bugfix Advisory 2015:0748 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0748.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6028eb7fd61883f440b98464a64e4ea9046b940fb71ca21910403d76d1ec1f9a amanda-2.6.1p2-9.el6_6.i686.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

hello list, I am attempting to ssh via a user account setup for amanda backups from the backup server to the test backup client. AFAIK everything is setup correctly yet when I ssh as the user to the client I have to type the password. the public key is in the authorized_keys file of the client and permissions all seem correct. Here is a verbose output of the ssh session [amandabackup at

CentOS Errata and Bugfix Advisory 2013:0427 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0427.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 3bbffdc2b0f669627853199868cf58cc3397e0f108fb856b54421271399359d9 amanda-2.6.1p2-8.el6.i686.rpm 4e1e14f387dfbb9d2658aec76eb9585edca1de73e0600e245da0eb4a395dd884

Hello, we are using amanda for backup with 2 tape libraries. Last days we made CentOS 7 update to CentOS Linux release 7.6.1810 (Core) Includes from base repository: amanda-client-3.3.3-21.el7.x86_64 amanda-server-3.3.3-21.el7.x86_64 amanda-3.3.3-21.el7.x86_64 amanda-libs-3.3.3-21.el7.x86_64 deleted: version 3.3.3-17 Before the update (= version 3.3.3-17) we run to configs in parallel without

CentOS Linux release 7.1.1503 (Core) amanda-3.3.3-13.el7.x86_64 amanda-client-3.3.3-13.el7.x86_64 amanda-libs-3.3.3-13.el7.x86_64 dump-0.4-0.22.b44.el7.x86_64 Hi, I have been using amanda backup for quite a long time now. I'm busy migrating some older hosts to CentOS 7 but have found that the available amanda packages (see above) have not been compiled on a host that has the 'dump'

CentOS Errata and Bugfix Advisory 2011:1539 Upstream details at : http://rhn.redhat.com/errata/RHBA-2011-1539.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 26faeaceb119c3b27d50abf8c55c7da5 amanda-2.5.0p2-9.el5.i386.rpm 5ced8d685aba893883dcb15bf1955cb3 amanda-2.5.0p2-9.el5.x86_64.rpm 3f3e3b4da4e779db6c577f4ce303c311

OK, after beating my head against the wall for an hour or so, I finally figured out why I could not ssh from a MacMini (running MacOSX 10.11.6) to my Linux Desktop (running CentOS 6), using the amandabackup account with public key authentification. SELinux! It seems the SELinux won't allow this if the target user's "home" directory is does not have a <mumble>_home_t

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When