similar to: fts_read failed

Displaying 20 results from an estimated 800 matches similar to: "fts_read failed"

2016 Oct 21
2
winbindd losing track of RFC2307 UIDs
On Tue, 4 Oct 2016, Achim Gottinger wrote: > Am 03.10.2016 um 18:57 schrieb Rob via samba: >> [...] >> >> This generally works fine... user mappings are like: >> >> $ wbinfo -i auser >> auser:*:10028:10000:User Name:/home/auser:/bin/bash >> $ id auser >> uid=10028(auser) gid=10000(agroup) groups=10000(agroup),10007(othergroup) >>
2016 Oct 04
0
winbindd losing track of RFC2307 UIDs
Am 03.10.2016 um 18:57 schrieb Rob via samba: > Hi all, > > I've been experiencing an intermittent problem where some UIDs on a > member server spontaneously change from being their AD-derived values > to being allocated from the default idmap space, even when there is no > change to the AD user information. > > Specifically, I have a member server running Samba
2016 Oct 03
0
winbindd losing track of RFC2307 UIDs
On Mon, 3 Oct 2016 12:57:54 -0400 (EDT) Rob via samba <samba at lists.samba.org> wrote: > Hi all, > > I've been experiencing an intermittent problem where some UIDs on a > member server spontaneously change from being their AD-derived values > to being allocated from the default idmap space, even when there is > no change to the AD user information. > >
2016 Oct 22
0
winbindd losing track of RFC2307 UIDs
Am 21.10.2016 um 18:40 schrieb Rob via samba: > On Tue, 4 Oct 2016, Achim Gottinger wrote: > >> Am 03.10.2016 um 18:57 schrieb Rob via samba: >>> [...] >>> >>> This generally works fine... user mappings are like: >>> >>> $ wbinfo -i auser >>> auser:*:10028:10000:User Name:/home/auser:/bin/bash >>> $ id auser >>>
2016 Oct 04
0
winbindd losing track of RFC2307 UIDs
Am 04.10.2016 um 10:21 schrieb Rowland Penny: > On Tue, 4 Oct 2016 02:35:21 +0200 > Achim Gottinger via samba <samba at lists.samba.org> wrote: > >> >> Am 03.10.2016 um 18:57 schrieb Rob via samba: >>> Hi all, >>> >>> I've been experiencing an intermittent problem where some UIDs on a >>> member server spontaneously change from
2016 Oct 04
2
winbindd losing track of RFC2307 UIDs
On Tue, 4 Oct 2016 02:35:21 +0200 Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > Am 03.10.2016 um 18:57 schrieb Rob via samba: > > Hi all, > > > > I've been experiencing an intermittent problem where some UIDs on a > > member server spontaneously change from being their AD-derived > > values to being allocated from the default
2016 Oct 04
0
winbindd losing track of RFC2307 UIDs
Am 04.10.2016 um 15:43 schrieb Rowland Penny via samba: > On Tue, 4 Oct 2016 15:16:17 +0200 > Achim Gottinger via samba <samba at lists.samba.org> wrote: > >> >> Am 04.10.2016 um 10:21 schrieb Rowland Penny: >>> On Tue, 4 Oct 2016 02:35:21 +0200 >>> Achim Gottinger via samba <samba at lists.samba.org> wrote: >>> >>>> Am
2016 Oct 03
6
winbindd losing track of RFC2307 UIDs
Hi all, I've been experiencing an intermittent problem where some UIDs on a member server spontaneously change from being their AD-derived values to being allocated from the default idmap space, even when there is no change to the AD user information. Specifically, I have a member server running Samba 4.4.5 on CentOS 6.8. AD service is provided by two Samba 4.4.5 servers. The member
2016 Oct 04
2
winbindd losing track of RFC2307 UIDs
On Tue, 4 Oct 2016 15:16:17 +0200 Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > Am 04.10.2016 um 10:21 schrieb Rowland Penny: > > On Tue, 4 Oct 2016 02:35:21 +0200 > > Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > >> > >> Am 03.10.2016 um 18:57 schrieb Rob via samba: > >>> Hi all, >
2016 Oct 04
0
winbindd losing track of RFC2307 UIDs
Am 04.10.2016 um 17:05 schrieb Rowland Penny via samba: > On Tue, 4 Oct 2016 16:09:40 +0200 > Achim Gottinger via samba <samba at lists.samba.org> wrote: > >> >> Am 04.10.2016 um 15:43 schrieb Rowland Penny via samba: >>> On Tue, 4 Oct 2016 15:16:17 +0200 >>> Achim Gottinger via samba <samba at lists.samba.org> wrote: >>> >>>>
2016 Oct 04
2
winbindd losing track of RFC2307 UIDs
On Tue, 4 Oct 2016 16:09:40 +0200 Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > Am 04.10.2016 um 15:43 schrieb Rowland Penny via samba: > > On Tue, 4 Oct 2016 15:16:17 +0200 > > Achim Gottinger via samba <samba at lists.samba.org> wrote: > > > >> > >> Am 04.10.2016 um 10:21 schrieb Rowland Penny: > >>> On
2007 Aug 26
1
RE: migrating samba to new hardware and different OS
Hi All I have done as much as I can to try and figure out what is going wrong with my samba migration by googleing and reading mailing list archives and reading documentation etc. I have an existing SAMBA 3.0.5 domain running on suse linux 9.3. I am trying to migrate this setup to a new server which is running Fedora Core 6 smbd 3.0.24-7.fc6 I have migrated the data across to the new system
2007 Aug 26
0
RE: migrating samba to new hardware and different OS [SOLVED]
Hi Guys Thanks a lot this has helped me greatly. The basics are now working i just have to migrate the rest of the user accounts and all will be well. :) Regards Andrew On 8/26/07, Julian Pilfold-Bagwell <jools@oss4all.plus.com> wrote: > Volker Lendecke wrote: > > On Sun, Aug 26, 2007 at 03:12:30PM +0200, Andrew Jeremy Gargan wrote: > > > > > >> write list
2013 Jan 07
0
access a file on one node, split brain, while it's normal on another node
Hi, everyone: We have a glusterfs clusters, version is 3.2.7. The volume info is as below: Volume Name: gfs1 Type: Distributed-Replicate Status: Started Number of Bricks: 94 x 3 = 282 Transport-type: tcp We native mount the volume in all nodes. When we access the file ?/XMTEXT/gfs1_000/000/000/095? on one nodes, the error is split brain. While we can access the same file on
2003 Dec 01
0
No subject
force user (S) This specifies a UNIX user name that will be assigned as the default user for all users connecting to this service. This is useful for sharing files. You should also use it carefully as using it incorrectly can cause security problems. This user name only gets used once a connection is established. Thus clients still need to connect as a valid user and supply a valid password. Once
2010 Jun 25
7
Ability to deploy a "skeleton" directory
Hi, I''d like to be able to deploy a skeleton directory through puppet, i.e. puppet deploys it only if it does not exist. I tried this : file {"/path/to/this/directory": source => "puppet:///files/path/to/the/skeleton", ensure => directory, recurse => true, owner => auser, group => agroup } But I have 2 problems for the moment : - if I
2011 Jun 28
0
[Gluster-devel] volume rebalance still broken
Replying and adding gluster-users. That seems more appropriate? ________________________________________ From: gluster-devel-bounces+jwalker=gluster.com at nongnu.org [gluster-devel-bounces+jwalker=gluster.com at nongnu.org] on behalf of Emmanuel Dreyfus [manu at netbsd.org] Sent: Tuesday, June 28, 2011 6:51 AM To: gluster-devel at nongnu.org Subject: [Gluster-devel] volume rebalance still broken
2006 Mar 29
3
ON 20060327 and upcoming solaris 10 U2 / coreutils
So, I noticed that a lot of the fixes discussed here recently, including the ZFS/NFS interaction bug fixes and the deadlock fix has made it into 20060327 that was released this morning. My question is whether we''ll see all these up to the minute bug fixes in the Solaris 10 update that brings ZFS to that product, or if there is a specific date where no further updates will make it in to
2016 Nov 02
1
Samba using pdb ldapsam fails upon startup
Dear all, I freshly installed a new smb-server that should act as file server with some smb-shares. The pdc is a Windows 2008 r2 server. My smb.conf is as follows: [global] workgroup = agroup server string = ssmbserver #passdb backend = tdbsam map to guest = Bad User usershare allow guests = No security = domain wins support = No
2024 Oct 26
1
[smb.conf] How to get "rw r r" ?
On 25/10/2024 14:03, Havany via samba wrote: > Did you try 133 mask instead of 0133 ? > > We use to disable acl for this kind of share and do something like that : > > [share] > path = /a/share/path > create mask = 133 > directory mask = 022 > valid users = @agroup > write list = @sagroup > force group = @agroup > nt acl support = No Still no go: It's rwx