search for: somewhow

...if ( (byte_len < 0) || (byte_len > 512)) { DEBUG(0, ("decode_pw_buffer: incorrect password length (%d).\n", byte_len)); DEBUG(0, ("decode_pw_buffer: check that 'encrypt passwords = yes'\n")); return False; } So somewhow the byte_len of the password buffer (first 4 bits of the buffer) is not being set correctly. I've played with many different passwd chat scripts - all leading to the same problem.

On Tue, Dec 01, 2015 at 03:59:56PM +0100, Mateusz Guzik wrote: > CHROOT_IN/OUT around commandvf are definitely problematic. chroot should be > done in the child, which also removes the need to chroot out in the > parent. The CHROOT_IN/OUT business does need to be rewritten. Every instance where we currently do something like: CHROOT_IN; r = stat (fd, &statbuf); CHROOT_OUT

...CHROOT_OUT is mere chroot ("."), which suggests that that cwd for > virt-builder is "/". This means anything using aforementioned construct > has to use absolute paths, otherwise it looks names up against the real > "/". For current code it would make sense to somewhow check if all > passed paths are absolute (if not by code inspection, one can try to > cook up a systemtap script to verify such behaviour in-between chroots). > > As for a solution, forking off a process which chroots is definitely on > the right track. However, I would argue what...

...problematic. CHROOT_OUT is mere chroot ("."), which suggests that that cwd for virt-builder is "/". This means anything using aforementioned construct has to use absolute paths, otherwise it looks names up against the real "/". For current code it would make sense to somewhow check if all passed paths are absolute (if not by code inspection, one can try to cook up a systemtap script to verify such behaviour in-between chroots). As for a solution, forking off a process which chroots is definitely on the right track. However, I would argue what's really needed here i...

Is there a plugin that does this? * Provides ordering for columns in tables, asc and desc * Integrated with paginator * Reorders through AJAX calls * Gives access by API to the column being used and whether the order is asc or desc to be able to mark it in the header somewhow * Supports cells coming from different models -- fxn

Le 08/12/2018 ? 16:23, Pete Biggs a ?crit?: >> thanks for the suggestion. Indeed it seems I have a problem with >> glibc. Version is different between x86_64 and i386 and I have two >> glibc-common for x86_64. >> Trying to remove the old one request removing half of the system >> packages because of the dependancies. The newest cannot be removed. >> >>

Does the following setup have any chance of ever working without to many problems? Our mix of ~ 40 workstations (win98se & xp pro) get the home drive mapped in the netlogon script when connecting into the domain for win9x net use h: \\linux\homes for win xp net use h: \\linux\homes /persistent:no relevant sections of our redhat 7.3 w/ samba 2.2.8 smb.conf are: [global] ;; server name

...0m0.013s > > Curious is also that wbinfo returns different errors for the same > call: 1. failed to call wbcGetpwnam: WBC_ERR_WINBIND_NOT_AVAILABLE > 2. failed to call wbcGetpwnam: WBC_ERR_DOMAIN_NOT_FOUND This is I believe an artefact of the now fixed problem. > > The first somewhow tells me winbind got stuck or not responding in > time. The second is more the expected response as foo does not > provide a domain and "winbind use default domain" is set to it's > default no - not expected the time it takes to get to this finding. > > >> > &...

We''re pleased to announce version 0.0.3 of Net::LDAP, the first pure-Ruby LDAP library. Net::LDAP intends to be a feature-complete LDAP client which can access as much as possible of the functionality of the most-used LDAP server implementations. This library does not wrap any existing native-code LDAP libraries, creates no Ruby extensions, and has no dependencies external to Ruby.

...AIN_NOT_FOUND Could not get info for user foo real 0m59.304s user 0m0.051s sys 0m0.013s Curious is also that wbinfo returns different errors for the same call: 1. failed to call wbcGetpwnam: WBC_ERR_WINBIND_NOT_AVAILABLE 2. failed to call wbcGetpwnam: WBC_ERR_DOMAIN_NOT_FOUND The first somewhow tells me winbind got stuck or not responding in time. The second is more the expected response as foo does not provide a domain and "winbind use default domain" is set to it's default no - not expected the time it takes to get to this finding. >> >> >>> He also...

> On 23 Feb 2019, at 14:52, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Sat, 23 Feb 2019 14:21:57 +0100 > Remy Zandwijk via samba <samba at lists.samba.org> wrote: > >> >> >>> On 23 Feb 2019, at 14:07, Rowland Penny via samba >>> <samba at lists.samba.org> wrote: >>> >>> On Sat, 23 Feb 2019