search for: bsdmem

Displaying 4 results from an estimated 4 matches for "bsdmem".

Did you mean: bsdman
2015 Jan 27
2
Can't get idmap_ad to work with winbind (only idmap_rid)
...me/TEST/krbtgt:/bin/false guest:*:100501:100514:Guest:/home/TEST/guest:/bin/false So the TEST:range is respected now. But User Shell and Home Dir from the UNIX attributes in the AD are still ignored. There's log entries in the AD member server's log.winbindd stating "Added (BUILTIN|BSDMEM|TEST.BUERGER-ENERGIE-BERLIN.DE) ...". My log.winbindd-dc-connect is completely empty, though! Is this a first clue? It would be no problem to go with the RID backend for now. But as I understand, this might give trouble should I ever trust domains from another forest in the future. With a...
2015 Jan 27
2
Can't get idmap_ad to work with winbind (only idmap_rid)
.../home/TEST/guest:/bin/false >> >> So the TEST:range is respected now. But User Shell and Home Dir >> from the UNIX attributes in the AD are still ignored. >> >> There's log entries in the AD member server's log.winbindd >> stating "Added (BUILTIN|BSDMEM|TEST.BUERGER-ENERGIE-BERLIN.DE) >> ...". My log.winbindd-dc-connect is completely empty, though! Is >> this a first clue? >> >> It would be no problem to go with the RID backend for now. But >> as I understand, this might give trouble should I ever trust >&g...
2015 Jan 27
0
Can't get idmap_ad to work with winbind (only idmap_rid)
...est:*:100501:100514:Guest:/home/TEST/guest:/bin/false > > So the TEST:range is respected now. But User Shell and Home Dir from > the UNIX attributes in the AD are still ignored. > > There's log entries in the AD member server's log.winbindd stating > "Added (BUILTIN|BSDMEM|TEST.BUERGER-ENERGIE-BERLIN.DE) ...". My > log.winbindd-dc-connect is completely empty, though! Is this a first > clue? > > It would be no problem to go with the RID backend for now. But as I > understand, this might give trouble should I ever trust domains from > another...
2015 Jan 27
0
Can't get idmap_ad to work with winbind (only idmap_rid)
...n/false >>> >>> So the TEST:range is respected now. But User Shell and Home Dir >>> from the UNIX attributes in the AD are still ignored. >>> >>> There's log entries in the AD member server's log.winbindd >>> stating "Added (BUILTIN|BSDMEM|TEST.BUERGER-ENERGIE-BERLIN.DE) >>> ...". My log.winbindd-dc-connect is completely empty, though! Is >>> this a first clue? >>> >>> It would be no problem to go with the RID backend for now. But >>> as I understand, this might give trouble should I...