IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
- Install winbind daemon, client programs, nss and pam libraries
- Removed codepage stuff so spec file works with current HEAD branch
(This used to be commit 04005e74c6f897ba9965b89210d06212486eeac7)
built as non-root user, assuming you have permissions set up properly
in your /usr/src/redhat directory.
Added nsswitch sub-target to all target.
(This used to be commit 109840bb3abd75370e8ec14bf08bae35d04bcdaf)
- can now use --with-winbind to force compilation on systems that are
not linux or solaris (-:
- don't compile winbind if the unix domain socket test fails
- compile right number of bits if --with-pam used
(This used to be commit d77295ee701ecad4d563efe0632bea81b69f78a0)
--with-pam passed to configure.
Fixed nsswitch target to compile the sbin and lib winbind targets.
Winbind still doesn't install its lib targets (libnss_winbind.so and
pam_winbind.so) properly - the install script is a big mess. )-:
(This used to be commit fc83346a43ba59efcdf415437e6b99e68d2561c5)
push calls. If this breaks authentication then good, it needed fixing anyway :-).
Jeremy.
(This used to be commit e3580b4033c551e215cb246d4e36c4870cb4a582)
According to the incorruptible judges find and grep, the latter won.
Mmm - procrastination. (-:
(This used to be commit 2e339403605177b15d5185a8fdd1b06f3f043168)
a sbin program.
Currently the pam and nss modules are installed into @prefix@/sbin - I'm
not sure whether this is a good idea or not. Perhaps they should be left
in the build tree and copied across as needed by hand or a packaging tool.
(This used to be commit 09af934c4aa295bec494740d94de76e5e4497887)
breakage if there are problems. I will take this out tomorrow if it
causes too many problems.
(This used to be commit f4d9abcac7f8b8fc1b3d380b76fc8c95688b5d5d)
break code path that was invalid (ie. we were assuming
we could infer a non-levelII oplock when such an oplock
was detected - this may no longer be valid once we've
processed the break process dealing with the break will
change the state of it anyway.
This prevents the state where we get the following packet
trace :
client server
NTcreate ->
<- NTcreate resp
NTcreate ->
<- break to level II
ok - broken ->
<- break to none
Thanks to Alan Romeril for providing the trace that allowed
me to track this down.
Jeremy.
(This used to be commit c343e4f49070011986fc2ed4acd4ce690d5f1d71)
