search for: whwn

I am on a rh 7.2 machinr running samba. My clients are windows 2000 and whn using locl profiles I experience quick log-ons and quicj log-offs. Whwn I flag the client for roaming profiles, it seems to take many minutes to log off. The users roaming directory IS created and is populated with their user inoformation, one user has 300M of stuff.Which I thought was alot. When the user goes to log-off it takes many minutes to synch with the serve...

...registers as per CC, but this code results in segmentation fault when compliled with O1 because makewt has value of *ip in R14 register and that is stored and restore by makewt at begining of call but due to tail call optimization following code is generated and here bitrv2 does not preserve R14 so whwn execution returns to main (which is caller of makewt) value of *ip is gone from R14 (which sould not) and when main calls makewt again then value of *ip (R14) is wrong and result into segmentation fault. Assembly code of makewt: _makewt: ... popq %rbx popq %r12 popq %r13 popq %r14...

...code results in segmentation fault when compliled with O1 because makewt > has value > of *ip in R14 register and that is stored and restore by makewt at > begining of call > but due to tail call optimization following code is generated and here > bitrv2 does > not preserve R14 so whwn execution returns to main (which is caller of > makewt) > value of *ip is gone from R14 (which sould not) and when main calls makewt > again > then value of *ip (R14) is wrong and result into segmentation fault. > > Assembly code of makewt: > _makewt: > ... > popq...

...tion fault when compliled with O1 because makewt >> has value >> of *ip in R14 register and that is stored and restore by makewt at >> begining of call >> but due to tail call optimization following code is generated and here >> bitrv2 does >> not preserve R14 so whwn execution returns to main (which is caller of >> makewt) >> value of *ip is gone from R14 (which sould not) and when main calls >> makewt again >> then value of *ip (R14) is wrong and result into segmentation fault. >> >> Assembly code of makewt: >> _make...

...but this > code results in segmentation fault when compliled with O1 because makewt has value > of *ip in R14 register and that is stored and restore by makewt at begining of call > but due to tail call optimization following code is generated and here bitrv2 does > not preserve R14 so whwn execution returns to main (which is caller of makewt) > value of *ip is gone from R14 (which sould not) and when main calls makewt again > then value of *ip (R14) is wrong and result into segmentation fault. > > Assembly code of makewt: > _makewt: > ... > popq %rbx >...

...d with O1 because makewt >>> has value >>> of *ip in R14 register and that is stored and restore by makewt at >>> begining of call >>> but due to tail call optimization following code is generated and here >>> bitrv2 does >>> not preserve R14 so whwn execution returns to main (which is caller of >>> makewt) >>> value of *ip is gone from R14 (which sould not) and when main calls >>> makewt again >>> then value of *ip (R14) is wrong and result into segmentation fault. >>> >>> Assembly code of...

...ting to ldif converting to sambaSamAccount and applying the edited ldif (some where along the line we also tried pdbedit -i ldapsam_compat:/oldserver) and configure the backend as ldap:ldapsam://localhost At a certain point we got everything to look ok when working from the two linux servers. Whwn we try browsing from one of our XP Pro computers (that authenticates and logs on against the PDC main server) for the temporary server (BDC) we can find the server but can't see the shares. It complains that the network name is no longer valid. After trying every thing I could think of I de...

...t;>> makewt has value >>>> of *ip in R14 register and that is stored and restore by makewt at >>>> begining of call >>>> but due to tail call optimization following code is generated and here >>>> bitrv2 does >>>> not preserve R14 so whwn execution returns to main (which is caller of >>>> makewt) >>>> value of *ip is gone from R14 (which sould not) and when main calls >>>> makewt again >>>> then value of *ip (R14) is wrong and result into segmentation fault. >>>> >>&g...

Hello, I am doing a samba pdc with ldap. When I try to login to the domain, or access some shares I get this in my ldap logs: Mar 7 16:46:16 localhost slapd[3588]: conn=25 op=4 SRCH base="ou=People,dc=test,dc=org" scope=1 filter="(&(objectClass=posixAccount)(uid=DOMAIN\5CTD))" Mar 7 16:46:16 localhost slapd[3588]: conn=25 op=4 SEARCH RESULT tag=101 err=0 text= My

Hello, I am doing some testing on a PXA270 based processor (on a single board computer) which makes the processor vulnerable to bit flips. One such bit flips seems to have corrupted the file system. The debug port on the board (it is a single board computer) had the following message when i think the FS corruption occured : <7>init_special_inode: bogus i_mode (33061) init_special_inode:

...iled with O1 because makewt has value >>>>>> of *ip in R14 register and that is stored and restore by makewt at begining of call >>>>>> but due to tail call optimization following code is generated and here bitrv2 does >>>>>> not preserve R14 so whwn execution returns to main (which is caller of makewt) >>>>>> value of *ip is gone from R14 (which sould not) and when main calls makewt again >>>>>> then value of *ip (R14) is wrong and result into segmentation fault. >>>>>> >>>>&gt...