search for: comatible

I have setup a Samba PDC with LDAP by the Samba howto. All is working fine. But when I try to add machine accounts it is giving me errors. The error is as such First I did #smbldap-useradd -w comat67$ This was successful. Then when I do this oblix:/home# pdbedit -a -m -u comat67$ Searching for:[(&(objectClass=sambaDomain)(sambaDomainName=COMAT))] smbldap_open_connection: connection

...or all protocols. .. NOTE: IPTables::Parse does not yet parse user defined chains and so it is possible your firewall config is compatible with psad anyway. ----------------------------------------------------------------------------------------------------- Is there a way for shorewall to be comatible with psad ? thanks & regards Petr Novak --- Odchoz? zpr?va neobsahuje viry. Zkontrolov?no antivirov?m syst?mem AVG (http://www.grisoft.cz). Verze: 6.0.520 / Virov? b?ze: 318 - datum vyd?n?: 18.9.2003

Hi, I have a puppet master and agent installed. I want to generate and configure master-agent certificate and followed the steps: Master: ========== 1. Cleaned up all certificate on Master: [root@puppet-server manifests]# puppet cert sign --all No waiting certificate requests to sign [root@puppet-server manifests]# puppet cert clean --all notice: Revoked

Hi all, I'm thingking og switching all the test scripts to use /bin/bash instead of /bin/sh. The main reason is that /bin/sh on linux can mean one of two things; bash in bourne shell comatibility mode or dash. These two behave differently enough to make it a pain to be always testing them. The other issue is that using some bash features will allow me to reuse code and reduce the amount of

Op 25-11-14 om 23:39 schreef Jan Stary: > Is there a reason the test scripts are calling bash? The change from sh to bash was made a little more than a year ago. The mailing list thread accompanying this change can be found here: http://lists.xiph.org/pipermail/flac-dev/2013-September/004374.html

> On Fri, 2003-09-19 at 07:10, Tom Eastep wrote: > > On Fri, 2003-09-19 at 06:59, Tom Eastep wrote: > > > On Fri, 2003-09-19 at 06:52, Petr Novák wrote: > > > > > > > Is there a way for shorewall to be comatible with psad ? > > > > > > >From the above messages, it doesn''t seem likely. > > > > > > > Investigate the FW_MSG_SEARCH parameter in psad -- looks like you need > > to set that to "Shorewall:" or something similar. > > >...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I changed all rules to drop (Even the one in shorewall.conf) .. And PSAD works great with Shorewall here ... Although that might not be what you want. Lady Linux At 10:43 AM 9/19/2003, you wrote: >Is there a way for shorewall to be comatible with psad ? >thanks & regards >Petr Novak "No Problems Only Solutions" Francesca C. Smith Lady Linux Internet Services fsmith@ladylinux.com -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com> iQA/AwUBP2sggm9MXAhl3ducEQLo3...

On Nov 25 23:56:05, mvanb1 at gmail.com wrote: > Op 25-11-14 om 23:39 schreef Jan Stary: > > Is there a reason the test scripts are calling bash? > > The change from sh to bash was made a little more than a year > ago. The mailing list thread accompanying this change can be > found here: > http://lists.xiph.org/pipermail/flac-dev/2013-September/004374.html How

JdL> I've always been afraid to ask, but here goes... JdL> What's the advantage of GUEST_SESSSETUP being a compile time parameter, JdL> instead of having it as an smb.conf parameter? I'd like to second this question! Also, just in case that it will not become an smb.conf parameter: can't it be added as a comment to the Makefile (probably near the comments to

...cfile provided with Samba is compatible with RHEL4. I don't build RHEL4 packages only because IMO if you pay for support for RedHat, installing non-vendor supplied packages would void your support agreement. Althought I could provide RPMS for the lates version of CentOS which should be binary comatible with RHEL4 systems. While I'm at it, is there any pressing need for 64-bit rpms as well? cheers, jerry ===================================================================== Samba ------- http://www.samba.org Centeris ----------- h...

...cfile provided with Samba is compatible with RHEL4. I don't build RHEL4 packages only because IMO if you pay for support for RedHat, installing non-vendor supplied packages would void your support agreement. Althought I could provide RPMS for the lates version of CentOS which should be binary comatible with RHEL4 systems. While I'm at it, is there any pressing need for 64-bit rpms as well? cheers, jerry ===================================================================== Samba ------- http://www.samba.org Centeris ----------- h...

On Nov 26 01:25:25, hans at stare.cz wrote: > On Nov 25 23:56:05, mvanb1 at gmail.com wrote: > > Op 25-11-14 om 23:39 schreef Jan Stary: > > > Is there a reason the test scripts are calling bash? > > > > The change from sh to bash was made a little more than a year > > ago. The mailing list thread accompanying this change can be > > found here: >

Hello, Can somebody of the Samba team explain me the difference of Fedora packages or Enterprise packages ( <http://enterprisesamba.com/> http://enterprisesamba.com/) of Samba on Red Hat Enterprise Linux 4? I tried to find any information about this subject, but googleing doesn't help me. The standard Samba package (3.0.10EL) of RHEL4 doesn't communicate with a W2k3 server

using samba and ldap - redhat 7.3 trying to work on a short cgi to update samba password (it is a url with attributes username and password). I am not very good at all with perl, so if someone can take a quick ponder and help me out, that would be great. I think that it fails in theory however, because to change other users password, you need to be root ... So I was wondering if anyone knows

Dear alltogether, I experience very strange behavior of imputation of NA's with the NORM library. I use R 2.2.0, win32. The code is below and the same dataset was also tried with MICE and aregImpute() from HMISC _without_ any problem. The problem is as follows: (1) using the whole dataset results in very strange imputations - values far beyond the maximum of the respective column, >