Displaying 8 results from an estimated 8 matches for "shared_".
Did you mean:
shared
2015 Oct 21
1
Can't get 'root preexec' to run
...re:
https://www.samba.org/samba/docs/using_samba/ch06.html
Does that mean that this "preexec" in the [homes] section is not invoked
if the user is accessing his or her home dir that is _configured_ on the
DC ("known" by the DC), but only if the home dir is actually
_located/shared_ there under \\dc\homes?
Seems logical now. :-/
So I could put my preexec part under [netlogon], right?
Am 21.10.2015 um 11:12 schrieb Ole Traupe:
> Louis, thanks for the idea!
>
> I can execute the script as root on linux (tested this), because I do
> folder (zfs data set) creatio...
2017 Dec 04
0
gluster and nfs-ganesha
...Number of Bricks: 1 x 2 = 2
> Transport-type: tcp
> Bricks:
> Brick1: glnode1:/data/brick1/gv0
> Brick2: glnode2:/data/brick1/gv0
> Options Reconfigured:
> nfs.disable: on
> transport.address-family: inet
> cluster.enable-shared-storage: enable
>
> Volume Name: gluster_shared_storage
> Type: Replicate
> Volume ID: caf36f36-0364-4ab9-a158-f0d1205898c4
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 1 x 2 = 2
> Transport-type: tcp
> Bricks:
> Brick1: glnode2:/var/lib/glusterd/ss_brick
> Brick2: 192.168.0.95:/var/lib/glusterd/ss_brick
&g...
2017 Dec 02
2
gluster and nfs-ganesha
...b-cca9d77871c5
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: glnode1:/data/brick1/gv0
Brick2: glnode2:/data/brick1/gv0
Options Reconfigured:
nfs.disable: on
transport.address-family: inet
cluster.enable-shared-storage: enable
Volume Name: gluster_shared_storage
Type: Replicate
Volume ID: caf36f36-0364-4ab9-a158-f0d1205898c4
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: glnode2:/var/lib/glusterd/ss_brick
Brick2: 192.168.0.95:/var/lib/glusterd/ss_brick
Options Reconfigured:
transport.address-family:...
2017 Dec 04
2
gluster and nfs-ganesha
...Number of Bricks: 1 x 2 = 2
> Transport-type: tcp
> Bricks:
> Brick1: glnode1:/data/brick1/gv0
> Brick2: glnode2:/data/brick1/gv0
> Options Reconfigured:
> nfs.disable: on
> transport.address-family: inet
> cluster.enable-shared-storage: enable
>
> Volume Name: gluster_shared_storage
> Type: Replicate
> Volume ID: caf36f36-0364-4ab9-a158-f0d1205898c4
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 1 x 2 = 2
> Transport-type: tcp
> Bricks:
> Brick1: glnode2:/var/lib/glusterd/ss_brick
> Brick2: 192.168.0.95:/var/lib/glusterd/ss_brick
&g...
2015 Oct 20
5
Can't get 'root preexec' to run
Looks like my nfsv4 kerberos and root access problem.
In that case, root didnt have a kerberos ticket, and was not allowed to access the needed folder. I think this is a bit the same.
Creating the users and profiles shares from ADUC is working fine for me but
not scripted from user root.
Greetz,
Louis
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at
2008 Jan 08
2
[LLVMdev] Adding ClamAV to the llvm testsuite (long)
...f.c scanners.c sis.c
> snprintf.c special.c spin.c str.c suecrypt.c\
> table.c text.c tnef.c unarj.c unsp.c untar.c unzip.c upack.c
> upx.c uuencode.c vba_extract.c wwunpack.c yc.c)\
> $(addprefix clamscan_, \
> clamscan.c manager.c others.c treewalk.c)\
> $(addprefix shared_, \
> cdiff.c cfgparser.c getopt.c misc.c network.c options.c output.c
> sha256.c)\
> $(addprefix libclamav_regex_, \
> regerror.c, regfree.c, \
> regcomp.c, regexec.c, strlcpy.c)\
> $(addprefix libclamav_nsis_, \
> nulsft.c, bzlib.c, infblock.c, LZMADecode.c )
&...
2007 Dec 18
0
[LLVMdev] Adding ClamAV to the llvm testsuite (long)
Chris Lattner wrote:
> One way to do this is to add a "cut down" version of the app to the
> test suite.
I disabled optional features in clamav-config.h
>
>> 2. GPL license. Chris?
>
> Any open source license that allows unrestricted redistribution is
> fine in llvm-test
Ok, I have created a script that automatically checks out ClamAV
0.92-stable source code
2007 Dec 18
3
[LLVMdev] Adding ClamAV to the llvm testsuite (long)
On Mon, 17 Dec 2007, Evan Cheng wrote:
> We always welcome more tests. But it looks like there are two issues
> here.
>
> 1. The autoconf requirement. Is it possible to get one configuration
> working without the need for autoconf?
One way to do this is to add a "cut down" version of the app to the test
suite.
> 2. GPL license. Chris?
Any open source license that