similar to: Somebody had problem with long user names

To answer my own question of a week or so ago, as to whether RHAS3 users had got 3.0.11 to compile and execute (I had a plethora of errors): The Red Hat 3.0.11 SRPM from the Samba site compiled cleanly and runs fine (daemons and utilities) on my RHAS3 test rig, and on a RHAS3 update 4 production NAS server doubling as a Samba 3 server with 1150+ users of Unix/Linux and soon PDC Windows services.

List, both on RHAS3 update3, update 4, Samba source code 3.0.9 thru 11 gives SIGSEGVs on make check. Installing the buggers and trying to run them gives the same. *THOUGH*. The Red Hat beta 3.0.9 srpm at fr2.rpmfind.net comples and runs "like a little sun" ("net als een zonnetje", in Dutch). Anyone compiled Samba 3.0.11 on Red Hat RHAS3/RHEL3? Not "how", just

People have been experiencing problems with the subject line. AFAICS most of them haven't bothered to follow selected bits of the HOWTO. However, the former excludes all references to the idealx scripts, which I cannot use, since my DIT is set up completely differently from the idealx concept. I write my own, disjointed, shell and awk OpenLDAP scripts. Neither on my RHAS3 test rig (config as

Samba 3.0.11, 3.0.14a, 3.0.15pre1 on Red Hat RHAS3 Samba server is an NT4 PDC (no ADS) passdb backend = ldapsam I could try it out for myself, since I've a test machine besides my regular site. But I'd really rather have a definitive answer. I have POSIX ACLs working fine. In smb.conf I set "nt acl support = yes" (default anyway). Let's presume that I go and put all

List, Thanks tremendously to JC and JHT for guiding (nay, kicking) me toward getting ACLs to work on RHAS3. Reading the RH sysadmin guide about ACLs and searching elsewhere, as well as thinking for myself, were also a pre. Now for something completely different: High school in Amsterdam Netherlands: - RHAS3 - Samba 3.0.11 RPC, not ADS (no way we're upgrading while the bug reports keep

I'm having a similar problem where the configure just doesn't find the ldap libraries even though I've got the ldap-devel rpm installed and the libraries are in their normal location in /usr/lib. -TJ -----Original Message----- From: samba-bounces+tjencks=navis.com@lists.samba.org [mailto:samba-bounces+tjencks=navis.com@lists.samba.org] On Behalf Of Tony Earnshaw Sent: Wednesday,

Try the configure format below: LDFLAGS='-L/usr/local/openldap/lib' CPPFLAGS='-I/usr/local/openldap/include' ./configure --prefix=/usr/local/samba-3.0.12pre1 --with-ldap --with-ads --with-winbind --with-krb5=/usr/local/krb5-1.3.5 --with-libiconv=/usr/local/libiconv-1.9.1 That's from my own compile. Change the LDFLAGS as applicable. -----Original Message----- From:

Means "acclaim" in both Norwegian languages (there are new official rules out today for writing both of the 2 Indo-European Norwegian languages). What made me write this acclaim is the number of postings I've seen about Samba's instability - i.e. run-away processes, profiles going wrong, ACL problems and more. My (high school) site with around 80 w2k workstations, of which

People, I came to Samba 3 or 4 weeks ago and now have a successful ldapsam 3.0.11 PDC installation for 1150+ users (around 80 Win 2000 and XP workstations) running together with a DHCP server as an "afterthought" service on a RHAS3 NAS server. I adopted/adapted my already existent Openldap (2.2.17) DSE at that site) and wrote to this list about my experiences. For example I

Base: Red Hat RHAS3, PDC security = user Samba 3.0.14a Cups 1.1.17 Windows XP Pro Epson C42UX (cheap inkjet) USB to the server I was looking for an alternative to the immensely complicated Add Printer Wizard procedure (APW) detailed in chapter 19.6 of the Samba HOWTO guide. The following is a method that works for me, I don't necessarily expect it to work for others, and I'd value any

Johan B, please let it through+ The headers are needed. I live in the Netherlands, where the police contacts for this sort of thing are grey and unknown to me. The Metropolitan Police (London only) in England is 100% on the ball, but they're under resourced and I don't live in their "manor" (London slang for area). I'd like to push it out to as powerful an organization

List, No, no questions, no complaints. Just compliments to the Samba team. Samba 3.0.11 (Red Hat RHAS3) running as (one of 5 diverse Linux servers) PDC for all (75+) wk2000 and XP professional workstations on top of an 1,560+ OpenLDAP 2.2.17 backend at Barlaeus Gymnasium ("gymnasium" means "sort of high school for over-intelligent pupils whose parents just might happen to have

Hi, It's (possible|probable) that the above was included in the list postings in February last; at that time I hadn't even begun with Samba (use it in production now :). If so,please point me at the archives, if not, could someone please comment? >From the last SANS NewsBites (apologies for the line break in the URL for those using 76-character text MMUAs): WORMS, ACTIVE EXPLOITS,

Hi, especially John H. T :) I'm yet again plodding through chapter 14 of the Samba-HOWTO-Collection.pdf. Not because I can't make what's in it work for me, I did that long ago, I found out for myself, because a great deal of what's in it is wrong. I just got fed up with trying to get Nagios to work - I gave up, for various reasons and started on the Samba doco. At the risk of

List, from the Dutch "Computable" paper ICT tabloid and daily ICT subscribable mailing-list and so-called verwittigingsbrief/ad hoc news letter, partly translated into English by me ;) Dutch readers only: http://www.computable.nl/nieuws.htm?id=524000 "Manage Windows clients from Linux servers" blahblahblah Zenworks 7, the latest release of Novell's sysadmin suite".

List, documenters; I'd like to exchange notes about the official Samba 3 LDAP doco. I'd like to do this off list, since doing it on list would simply confuse and confound users wit perfectly working systems. Background: Me, Samba relative newbie, though I can get *everything* Samba-orientated to work simply by using umpteen years Unix experience. Many years as Openldap admin. With

Now it works and updates the zone like you said But now I get this For windows 7 Apr 22 20:25:45 cd1 named[1704]: samba_dlz: starting transaction on zone home.cu Apr 22 20:25:45 cd1 named[1704]: samba_dlz: disallowing update of signer=WIN28\$\@HOME.CU name=win28.home.cu type=AAAA error=insufficient access rights Apr 22 20:25:45 cd1 named[1704]: client 192.168.58.80#53235/key WIN28\$\@HOME.CU:

On Mon, Mar 10, 2014 at 6:52 PM, Schlomo Schapiro <schlomo at schapiro.org> wrote: > Hi, > > On 10 March 2014 18:13, Eric PEYREMORTE <eric.peyremorte at iut-valence.fr>wrote: > >> Ok i give up. I will stick with the old version version (4.07) which works >> well with dell 380 and 790. >> >> I tried to understand what happened between 4.07 and 5 but i

On Mon, Mar 10, 2014 at 7:55 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mon, Mar 10, 2014 at 7:15 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Mon, Mar 10, 2014 at 6:52 PM, Schlomo Schapiro <schlomo at schapiro.org> wrote: >>> Hi, >>> >>> On 10 March 2014 18:13, Eric PEYREMORTE <eric.peyremorte at iut-valence.fr>wrote:

Le 11/03/2014 10:32, Eric PEYREMORTE a ?crit : > Le 11/03/2014 00:56, Gene Cumm a ?crit : >> On Mon, Mar 10, 2014 at 7:55 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> On Mon, Mar 10, 2014 at 7:15 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >>>> On Mon, Mar 10, 2014 at 6:52 PM, Schlomo Schapiro >>>> <schlomo at schapiro.org> wrote: