similar to: When will be released samba 3.0.20a with latest patches ?

Hi. There isn't a package httpd-2.0.52-41.ent.6.centos4 for centos4 in UPDATES repo. There is only a httpd-2.0.52-41.ent.6.centos4.src.rpm in SRC [http://mirror.centos.org/centos/4/updates/SRPMS/?C=M;O=D] This is probably a bug. Package httpd doesn't build ? Jancio Wodnik -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I joined samba server (linux box centos 5.4) under samba 3.4.7 to Windows Domain at windows server 2003. wbinfo -g shows me all the groups from the AD and wbinfo -u shows me all the users. Then yesterday i upgraded to samba version 3.5.2, restarted windbind and smb. Then, when i make: wbinfo -g then i see nothing. wbinfo -u shows me all the user in Active Directory. In previous version

hi, it's been a few weeks since rhel/centos 5.4 released and there were many discussion about this new "feature" the weekly raid partition check. we've got a lot's of server with raid1 system and i already try to configure them not to send these messages, but i'm not able ie. i already add to the SKIP_DEVS all of my swap partitions (since i read it on linux-kernel list

Hi, Redhat announced RHEL 5.1 on Nov 07, so hopefully CentOS 5.1 will be ready shortly. But I get kind of nervous of the arrival of 5.1. My problem is: I have hundreds Centos 5.0 boxes just finished installation and I will continue to install and upgrade hundreds more in next few months. With the arrival of Centos 5.1, I don't like to reinstall them anymore but continuous upgrade instead

Hello everybody, had anyone of you problems with winbind and tdbfiles, when upgrading from 3.0.14a to 3.0.20a? The Symptom was: After upgrading to 3.0.20a the idmapping was corrupt. Although 3.0.20a runs fine, none of the idmaping was resolved correctly. Downgrading to 3.0.14a "restored" the idmaps. tdbdump showed me the same idmappings, therefor i think winbind wasn't able

Hello, I was using version 3.0.14 and upgraded to 3.0.20a. I did not change my config, however, I am seeing some serious problems now, and I am not sure what to do about it. I noticed there were a large number of changes between these two versions. I looked at the changes briefly, but there are just so many. This samba server is a domain memmber, on an ADS domain with a win 2003 enterprise

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== He's not the first psycho to hire us nor the last. You think that's a commentary on us? -- Capt. Malcolm Reynolds (Firefly 2002) =============================================================== Release Announcements =====================

Hello, Last week I downloaded and installed the 3.0.20a-23 release on Redhat ES 4 x86_64bit and noticed that I am getting the "Winbind Dead but subsys locked" status on winbind service. The service seems to start corectly but immediately get "Winbind Dead but subsys locked" status message. I had been running version 3.0.20-22 64 bit version which was also downloaded from

Hi, I solved following problem by upgrading GCC from version 3.0 to 3.4.2, and compiling samba-3.0.14a instead of 3.0.20a. The only problem I had during "make" with Samba-3.0.14a was: .... Compiling smbd/server.c Linking bin/smbd /usr/ccs/bin/ld: illegal option -- E .... Which was fixed by rename /usr/ccs/bin/ld to ld.sun. With newer version of GCC, I still have following error

Hi, All I am having error compiling Samba 3.2.10a on a Solaris 8 box, using gcc version 3.0. ./configure --prefix=/usr/local/samba-3.0.20a --with-pam --with-pam_smbpass --with-automount --with-quotas --with-acl-support --with-winbind --with-ldap --with-ads I got following: Using FLAGS = -I/usr/local/include -Wall -D_SAMBA_BUILD_ -I./popt -Iinclude

Here is the full "transaction" -- outgoing agentcall, to agent '1001', on 'Local/3044@local-4fee,1' -- Called Agent/1001 -- Executing Macro("Local/3044@local-4fee,2", "sipline|3044") in new stack -- Executing Dial("Local/3044@local-4fee,2", "SIP/3044|20|t") in new stack -- Called 3044 -- SIP/3044-ea92 is

I am getting this on the console once people call in -- outgoing agentcall, to agent '1001', on 'Local/3044@local-fd6d,1' -- Called Agent/1001 -- Executing Macro("Local/3044@local-fd6d,2", "sipline|3044") in new stack -- Executing Dial("Local/3044@local-fd6d,2", "SIP/3044|20|t") in new stack -- Called 3044 --

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =============================================================== He's not the first psycho to hire us nor the last. You think that's a commentary on us? -- Capt. Malcolm Reynolds (Firefly 2002) =============================================================== Release Announcements =====================

All - We are using 3.0.20a on SLES 9 and are trying to configure a member server for our NT4 domain. The wbinfo commands (-u and -g) show correct information. The getent commands (passwd and group) work fine also. If Samba is running without winbind, I can see the shares in the config file (net view \\xxxxxxxx) from a PC. With winbind running I get an error message about the computer name

Any ideas on this warning? If I call this number, sometimes I get this error and sometimes the call goes thru fine. Why would it work sometimes? -- Executing Goto("SIP/3044-8d49", "cytel-outgoing|915124512424|1") in new stack -- Goto (cytel-outgoing,915124512424,1) -- Executing SetCIDNum("SIP/3044-8d49", "2814494000") in new stack --

I'm currently running samba 3.0.20a I can configure and make 3.0.20a with no problem I run the same configure command on the 3.0.24 source, configure works fine, but make returns the following. ( and just to test if a patch screwed me up I tested configuring and making the 3.0.20a version again, and it worked as it should ) Any bugs with 3.0.24??? Using FLAGS = -O -D_SAMBA_BUILD_

Here is the setup: SIP/3044 -> SetCallerID(5551212) -> Call out PRI The CDR shows a src of 5551212. That is a lie! The src of that call was not 5551212, the source was 3044! The "translated source" of that call was 5551212. How can I get "real" source of this call and not some faky nonsense? The "reason" behind using the SetCallerID is because if I

Greetings, Our setup: Xeon 2x2.8Ghz/2GB RAM Red Hat Linux release 7.3 (Valhalla) Kernel 2.4.29 on an i686 multihomed - 5 subnets, samba operates only on 4 firewalled Samba: v3.0.20a Clients: Windows XP SP2 fully patched; MacOS X 10.3/10.4 We are having intermittent problems with nmbd/wins. At one point our admin users couldn't logon for upto 2 hours. When any of our user login into the

This just started happening today. I've got 1 queue and 6 agents. All logged in. I tell the service people to ignore my call if they see my caller id. I call the queue and watch as asterisk bounces me around the phones. Our agent ring time is 5 second timeout and a 5 second wait time before trying next agent. I get the same message in console for each agent attempt: -- Executing

In 3.0.20a/ldapsam the Usrmgr shows in the all users view the displayName attribute as full name, but in the user properties view the cn attribute. Seems a little bit inconsistent to me, shouldn't be the algorithm to retrieve the full name always the same? Daniel