There's a thread here:
https://github.com/zfsonlinux/zfs/issues/170 (I'm posting as
*fireappleblackhttps://github.com/fireappleblack
)*
...Which implies that the hold-up (from a zfs-linux perspective) is the
lack of richacls support in the mainstream kernel at the moment. (E.g.
OpenSuse supports
From a windows client I get network path not found as soon interface is
brought up, by either host name or ip address, but only on computers on the
same subnet as that interface. The log (finally) tells a story I can't
find a solution to:
May 1 06:16:41 nt-filer01 smbd[15036]: [2012/05/01
Hi
On 1 May 2012 00:24, sandy.napo...@eccmg.cupet.cu wrote:
Hello list, Iam running every day git pull for update my samba-master,
after I follow the step upgrading-samba4, and everything is ok, but I will
want know how I can see if my samba4 is upgrade succeful. thereis some
log. some
(Posted to Samba-technical, but probably should have cross posted here for
people interested in Samba4...)
I have created a Samba4 Project Status Wiki page at:
https://wiki.samba.org/index.php/Samba4/Status. Actually, the Status
page was already there, but hadn't been updated since about 2008.
Greetings,
I'm trying to configure samba in a pacemaker two-node (active/passive)
cluster. I am able to fail the services over from one node to another,
but when I do, I still need to run net ads join on the node before
client users can connect to a share.
In my smb.conf I am specifying
hello,
I have a wiered issue, some time when I run net ads join -U username,
some times I have see this error message, and some time it shows as
success. In between the error messages and success result, their are no
changes to any configuration, not sure what is causing this issue.
# net ads
The branch, master has been updated
via 9705a70 move VERSION to alpha21
via edb15ff prepare WHATSNEW for alpha20 and mark as release
from 8135576 s4-upgradedns: Update serverdn with only the attributes
that have changed
The branch, master has been updated
via b985c67 s3:selftest run LOCAL-IDMAP-TDB-COMMON in make test
via 55870b0 s3:torture: add idmap_tdb_common test code
via 0e06d94 s3:winbindd/idmap_tdb: use idmap_tdb_common code
via 15b12cb s3:winbindd/idmap_tdb2: fix logic
The annotated tag, samba-4.0.0alpha20 has been created
at 33f767d0d564fa219fbe9715f457a2ae34a67729 (tag)
tagging edb15ffef29fbb69a4d1dfc862fe8d6a3a027347 (commit)
replaces ldb-1.1.6
tagged by Andrew Bartlett
on Tue May 1 18:53:02 2012 +1000
- Log
The autobuild test system has detected an intermittent failing test in
the current master tree.
The autobuild log of the failure is available here:
http://git.samba.org/autobuild.flakey/2012-05-01-1207/flakey.log
The samba3 build logs are available here:
The autobuild test system has detected an intermittent failing test in
the current master tree.
The autobuild log of the failure is available here:
http://git.samba.org/autobuild.flakey/2012-05-01-1407/flakey.log
The samba3 build logs are available here:
The autobuild test system has detected an intermittent failing test in
the current master tree.
The autobuild log of the failure is available here:
http://git.samba.org/autobuild.flakey/2012-05-01-1608/flakey.log
The samba3 build logs are available here:
The autobuild test system has detected an intermittent failing test in
the current master tree.
The autobuild log of the failure is available here:
http://git.samba.org/autobuild.flakey/2012-05-01-1807/flakey.log
The samba3 build logs are available here:
The autobuild test system has detected an intermittent failing test in
the current master tree.
The autobuild log of the failure is available here:
http://git.samba.org/autobuild.flakey/2012-05-01-2007/flakey.log
The samba3 build logs are available here:
The autobuild test system has detected an intermittent failing test in
the current master tree.
The autobuild log of the failure is available here:
http://git.samba.org/autobuild.flakey/2012-05-01-2208/flakey.log
The samba3 build logs are available here:
The autobuild test system has detected an intermittent failing test in
the current master tree.
The autobuild log of the failure is available here:
http://git.samba.org/autobuild.flakey/2012-05-02-0010/flakey.log
The samba3 build logs are available here:
The branch, master has been updated
via d7f3c00 s3:torture fix flakey testcase
from b985c67 s3:selftest run LOCAL-IDMAP-TDB-COMMON in make test
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -
commit
The branch, master has been updated
via 5763301 selftest: run more raw.samba3 against secshare simple file
server
via 6d87df2 selftest: Run smbtorture tests being run against s3dc
against plugin_s4_dc as well
via 53c70be selftest: Do not start samba4 srvsvc in
The branch, master has been updated
via 7b55ec2 s4-provision: Fix up --use-s3fs to create the directory for
xattr.tdb
via b6b4364 s4-wintest: --use-s3fs in wintest
via 63f2d10 s4-provision: Fix --use-s3fs to parse correctly
via 9712912 testsuite/libsmbclient:
19 matches
Mail list logo
