search for: 10028

Hi, May be this helps: dat1<- read.table(text=" pbnr??????? dat? dep? dys? sop? ago? mis age female 1 10023 1994-02-21 0.75 1.00 0.50 0.50 0.75? 35????? 1 2 10023 1994-05-25 0.75 1.00 0.50 0.50 0.75? 35????? 1 3 10028 1994-02-01 2.00 1.75 3.00 0.50 1.50? 42????? 1 4 10028 1999-01-15 1.25 0.75 2.25 0.50 0.25? 42????? 1 5 10053 1994-03-16 2.50 0.75 1.25 0.50 1.25? 22????? 1 6 10053 1994-09-23 3.25 1.25 1.25 0.75 2.25? 22????? 1 ",sep="",header=TRUE,stringsAsFactors=FALSE) dat1$dat<- as.Date(dat1$...

...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...

...# Use template settings for login shell and home directory winbind nss info = template template shell = /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...

...: head(scltotal) pbnr dat dep dys sop ago mis age female messpunkt2 messpunkt1 tage eintrittsjahr 1 10023 1994-02-21 0.75 1.00 0.50 0.50 0.75 35 1 8817 8817 0 1994 2 10023 1994-05-25 0.75 1.00 0.50 0.50 0.75 35 1 8910 8817 93 1994 3 10028 1994-02-01 2.00 1.75 3.00 0.50 1.50 42 1 8797 8797 0 1994 4 10028 1999-01-15 1.25 0.75 2.25 0.50 0.25 42 1 10606 8797 1809 1999 5 10053 1994-03-16 2.50 0.75 1.25 0.50 1.25 22 1 8840 8840 0 1994 6 10053 1994-09-23 3.25 1.25 1.25...

...te > > template shell = /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: > > > > $...

...gt;>>> 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...

.../%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 >>&...

...of shares, "common", "user" and "nov" On our common-share, I created a document with MS Word (Windows 7-client): $ sudo smbstatus | grep .doc WARNING: The "idmap uid" option is deprecated WARNING: The "idmap gid" option is deprecated 14285 10028 DENY_WRITE 0x12019f RDWR NONE /mnt/storage/share/common New Microsoft Office Word Document.docx Fri Mar 6 09:29:04 2015 I kept word running and after 1? hours these messages appears in the log: $ tail -f /var/log/samba/log.myIP [2015/03/06 11:04:31.126911, 1] ../source...

...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 coup...

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

...e directory > winbind nss info = template > template shell = /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...

...s fine... user mappings are like: You might think it works fine, but it will probably work better if you change 'idmap config MY.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:1000...

...shell = /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: >...

On Tue, 4 Oct 2016 12:29:19 -0400 (EDT) Rob via samba <samba at lists.samba.org> wrote: > > On Tue, 4 Oct 2016, Rob wrote: > > > On Mon, 3 Oct 2016, Rowland Penny wrote: > > > >> On Mon, 3 Oct 2016, Rob wrote: > >>> # idmap config for domain > >>> idmap config MY.AD.REALM.COM:backend = ad > >>>

...droid-x86.org/releases/releasenote-4-4-r5.html). I can succesfully mount samba shares from the android "terminal emulator", with the following command, for example: --- # android_share su root busybox mount -v -t cifs \ -o username=andy,password=pass,nounix,nosuid,nodev,noexec,noatime,gid=10028,uid=10023,rw \ //192.168.213.133/android_share /sdcard/android_share --- So far so good. Now I have just upgraded the server machine to "clear linux release 33490". Only the full system upgrade has been performed, with no other changes. After the upgrade, the samba version has been updat...

...of shares, "common", "user" and "nov" On our common-share, I created a document with MS Word (Windows 7-client): $ sudo smbstatus | grep .doc WARNING: The "idmap uid" option is deprecated WARNING: The "idmap gid" option is deprecated 14285 10028 DENY_WRITE 0x12019f RDWR NONE /mnt/storage/share/common New Microsoft Office Word Document.docx Fri Mar 6 09:29:04 2015 I kept word running and after 1? hours these messages appears in the log: $ tail -f /var/log/samba/log.myIP [2015/03/06 11:04:31.126911, 1] ../source3/smbd/service.c...

...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 >>> 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: &g...

...>> Have you compared the users AD objects ? > > Running 'net cache flush' on the member does fix things, albeit only > for a while: > > # wbinfo -i auser > auser:*:2020:10000:User Name:/home/auser:/bin/bash > # net cache flush > # wbinfo -i auser > auser:*:10028:10000:User Name:/home/auser:/bin/bash > [...wait a few hours...] > # wbinfo -i auser > auser:*:2020:10000:User Name:/home/auser:/bin/bash > > Using ldbsearch on sam.ldb on the DC, I compared the attributes of > problematic users and normal users... I couldn't find anything ob...

...> > > > Hopefully that makes more sense. > > > > > > Personally I would do that with our python bindings. > > > > > > > i would be thrilled to get the Python stuff working. > > > > > https://bugzilla.samba.org/show_bug.cgi?id=10028 This is just about complete Python3 support. Python2 works fine with Python 2.6 or later (but please, please use 2.7), and the RPC stuff probably works with Python3. > AFAICT, it's not officially supported yet, right? No, these are part of the APIs we support > i.e. it's in majo...

On Mon, Jun 18, 2018 at 11:36 PM, Andrew Bartlett <abartlet at samba.org> wrote: > On Mon, 2018-06-18 at 15:56 -0400, pisymbol wrote: > > I have a binary based off of rpclient that prints out the raw share > > SD as a binary stream instead of trying to parse it into human > > readable format (the default behavior). That is what I'm after. > > > >