Barry R Cisna schrieb:
> Joerg,
>
> Thanks for the idea on winbind dyeing over time. Unfortunately that was
> not happening.
...
I was hoping I could figure out some sort of
> script to run as a cron job on early Monday morning to automate my
> workaround,,,? if you have any ideas on this let me
Barry R Cisna schrieb:
> Hello All,
>
> Samba 3.024 EL5 install
>
> This will seem like an odd one to all I am sure. I will explain.
...
> Problem. Every Monday morning when I get to school I have to ( or have a
> helper do it) either comment or uncomment
> -Original Message-
> From: Michael Davidson
> Sent: Friday, February 09, 2007 10:48 AM
>
> I have read many opinions on what character to use for the winbind
> separator. Many people urge changing the default to '+'. According
to
> testparm:
>
> 'winbind separator = +' might cause pro
If you want \ as winbind separator just don't specify one as it will
be correct with the default value.
cheeers,
henrik
18 okt 2006 kl. 23:24 skrev Karthik R:
Am able to read the domain users using winbind and samba. But while
executing wbinfo -u or wbinfo -g command, i get the winbind
separ
As I described below, the only config change I made was to remove
my setting for winbind separator char so it would default back to
"\" instead of the "-" I was using. Then all of the
make_server_info_from_pw failed errors went away.
Another user on the list was having the same issue and he's go
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| In 3.0.8, users connections would have the domain
| and separator char for spnego kerberos replies and
| if the separator is something other than
| the default of \, it will cause errors like this:
I don't think this is correc
On Thu, Feb 19, 2004 at 12:39:08PM +0100, Karel Kulhavy wrote:
> I tried putting \ instead of '\' into smb.conf but the config file even
> doesn't get parsed - it reports syntax error on the next line.
It should probably be escaped somehow, but I think it's easier to just
remove this line, since \
