search for: othergroup

Hello Im just been working with puppet, the first usecase i have is to set up a system to create users and then push ssh keys on this machines in the create users .ssh files. I just started with puppet so i am a bit cluesless, Can someone push me in the right direction? Im having a centos enviorment. -- You received this message because you are subscribed to the Google Groups "Puppet

...ell = /bin/bash template homedir = /home/%U winbind use default domain = yes [...] 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) After a while (generally a couple days, though sometimes much sooner), this starts happening: $ wbinfo -i auser auser:*:2018:10000:User Name:/home/auser:/bin/bash $ id auser uid=2018(auser) gid=10000(agroup) groups=10000(agroup),10007(othergroup) and this persists until I do "net cache fl...

...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) >> >> After a while (generally a couple days, though sometimes much sooner), this >> starts happening: >> >> $ wbinfo -i auser >> auser:*:2018:10000:User Name:/home/auser:/bin/bash >> $ id auser >> uid=2018(auser) gid=10000(agroup) groups=10000(ag...

...n = yes > > [...] > > > > 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) > > > > After a while (generally a couple days, though sometimes much > > sooner), this starts happening: > > > > $ wbinfo -i auser > > auser:*:2018:10000:User Name:/home/auser:/bin/bash > > $ id auser > > uid=2018(auser) gid=10000(agroup) > >...

...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) > >>> > >>> After a while (generally a couple days, though sometimes much > >>> sooner), this starts happening: > >>> > >>> $ wbinfo -i auser > >>> auser:*:2018:10000:User Name:/home/auser:/bin/bash > >>> $ id ause...

I need to play games with an expression similar to the following one: print(xyplot(DepVar ~ Group|Covar, groups=Othergroup, data=mydf, pch = 18 ,main="Testcase",auto.key = TRUE)) The problem is that the formula argument (the first argument) an the groups argument are passed over from another program as strings. The formula argument does not pose problems, I can do as.formula("DepVar ~ Group|Covar&qu...

...ome/%U > > winbind use default domain = yes > [...] > > 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) > > After a while (generally a couple days, though sometimes much sooner), > this starts happening: > > $ wbinfo -i auser > auser:*:2018:10000:User Name:/home/auser:/bin/bash > $ id auser > uid=2018(auser) gid=10000(agroup) groups=10000(agroup),10007(othergroup) > >...

...Y.AD REALM.COM' to 'idmap config MYDOMAIN' The 'ad' backend should start working properly then. Rowland > > $ 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) > > After a while (generally a couple days, though sometimes much > sooner), this starts happening: > > $ wbinfo -i auser > auser:*:2018:10000:User Name:/home/auser:/bin/bash > $ id auser > uid=2018(auser) gid=10000(agroup) > groups=10000(agroup),10007(othergroup) >...

...gt;>> >>> 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) >>> >>> After a while (generally a couple days, though sometimes much >>> sooner), this starts happening: >>> >>> $ wbinfo -i auser >>> auser:*:2018:10000:User Name:/home/auser:/bin/bash >>> $ id auser >>> uid=2018(auser) gid...

Hi, I have setup a linux shared directory using Samba. From windows XP, I can see the shared directory, browse it, read files from it; however, I can't write to it. I have changed the ownership of the shared directory in linux to "nobody", changed the group to "nobody", and chmod it 777. I have looked at threads for similar problems, but I can't get my problem

...os running, and joining the AD. But when I use id or wbinfo now to get user information I get lots of groups which cannot be mapped a GID and thus are displayed as -1 or 4294967295: id DOMAIN\\USER uid=3611(DOMAIN\\USER) gid=3000(DOMAIN\\PRIMARYGROUP) groups=3000(DOMAIN\\PRIMARYGROUP),3001(DOMAIN\\OTHERGROUP),4294967295,4294967295,4294967295,4294967295,4294967295,4294967295,4294967295,4294967295,4294967295,4294967295,4294967295,4294967295,4294967295,2(daemon) wbinfo -r DOMAIN\\USER 3000 3001 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 2 On another server running Samba3 only the two groups with GID 3000 an...

...>>> >>> 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) >>> >>> After a while (generally a couple days, though sometimes much >>> sooner), this starts happening: >>> >>> $ wbinfo -i auser >>> auser:*:2018:10000:User Name:/home/auser:/bin/bash >>> $ id auser >>> uid=2018(auser) gid=...

...> >>>>> > >>>>> $ 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) > >>>>> > >>>>> After a while (generally a couple days, though sometimes much > >>>>> sooner), this starts happening: > >>>>> > >>>>> $ wbinfo -i auser > >>>>> auser:*:2018:10000:User Name:/...

...ine... 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) >>>>> >>>>> After a while (generally a couple days, though sometimes much >>>>> sooner), this starts happening: >>>>> >>>>> $ wbinfo -i auser >>>>> auser:*:2018:10000:User Name:/home/auser:/bin/bash >>&...

...gt;>> >>>>>>> $ 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) >>>>>>> >>>>>>> After a while (generally a couple days, though sometimes much >>>>>>> sooner), this starts happening: >>>>>>> >>>>>>> $ wbinfo -i auser >>>>>>> auser:*:2018...

...llowUsers in combination with AllowGroups, only users who are specified in AllowUsers AND some of their group is in AllowGroups can login. Minimal test case: /etc/ssh/sshd_config >AllowUsers user >AllowGroups user user:user can log in /etc/ssh/sshd_config >AllowUsers user >AllowGroups othergroup user:user can NOT log in /etc/ssh/sshd_config >AllowUsers otheruser >AllowGroups user user:user can NOT log in Manual page states: > ".. The allow/deny directives are processed in the following order: DenyUsers, AllowUsers, DenyGroups, and finally AllowGroups." There is not me...

...the dual-homed box? Are both networks using the same workgroup name? You can also specify the IP address of the remote samba browse master (as opposed to the network address) like: remote announce = 130.98.6.2 and a (different) remote workgroup name like this: remote announce = 130.98.6.255/OTHERGROUP Any of the above (done correctly) should make the first (dual- homed) server show up in the NetHood of the remote network. Maybe you need to specify the remote announce parameter in the remote samba server and point it back at the first IP address. What do you have specified in smb.conf on th...

...of thoses groups and users. We use Samba 3 and a GNU/Debian sarge distribution. There is no problem to join the W2K network: $> net rpc join -U Administrator password: ... Joined domain MYDOMAIN. We see all groups and users: $> wbinfo -u guillaume foo faa fii ... $>wbinfo -g mygroup othergroup ... We can see the disk from the W2K network, no problems. The problem is that is I put as a valid users a user name it's not work: For exemple, my user name is guillaume and my group is mygroup: 1/ If I put in smb.conf the line: valid users = @mygroup it work, only members of mygroup (and...

...an exect the script (as is put in radiusd.conf) correct from the command line: Deb:~# /usr/bin/ntlm_auth --username=javi2 --require-membership-of='AAMM\MyGroup' --domain=AAMM password: NT_STATUS_OK: Success (0x0) Deb:~# /usr/bin/ntlm_auth --username=javi2 --require-membership-of='AAMM\OtherGroup' --domain=AAMM password: NT_STATUS_LOGON_FAILURE: Logon failure (0xc000006d) Deb:~# So samba and winbind look to be correctly configured, but when radius exect it, looks as if winbind couldn't resolve group's name. My line on radiusd.conf is: ntlm_auth = "/usr/bin/ntlm_auth --re...