search for: lowecase

...t. I was hoping there was just an option to turn on, but I didn't see one, and unfortunately I don't know enough C to change to lc($submitted_user) eq lc($database_user) like I would in perl :-) I do have control over generating the passwd file, and it is currently generating the users to lowecase in the file, so just lc($submitted_user) eq $database_user would work well enough. Unfortunately I don't know enough C to do that, so I thought I would ask if anyone has done this. So, does anyone have any ideas on how to do this? Thank you, -- andrew /-----------------------------------...

Hello all, I have a time format looks like 31JAN2002:00:00:00.000 How could I cut it to 31JAN2002 ? I tried with format() but not work. Thanks, Rebecca ---------------------------------------------------------------------- This message, and any attachments, is for the intended r...{{dropped:5}}

...input load / stores are not handled correctly, I see that the LOAD instructions get postfixed with a i reps. g for input / global how would I go about modifying the code emitter (AsmPrinter?) to change "LOADi" into "LOAD <dest> RINPUT <offset>"? 5) Talking about the lowecase suffixes to the instructions, these should not be part of the output, how do I filter these? 6) And finally, the current llvm-tgsi output uses e.g. TEMP1y where as for the destination it should use TEMP[1].y and for the sources it should use TEMP[1].xxxx (so include proper swizzling info). Lots o...

...hex digit and try - again. Ultimately, it will try looking for a file named "default" - (in lower case). + again. + + Next, it will search for the config file using the client architecture + type (using the DHCP client-architecture identifiers registered with + IANA), as a 4-digit lowecase hexadecimal number, prefixed with + "arch-". For example, an x86 UEFI machine (client architecture + 0x00 0x07) would request the filename "arch-0007". + + IANA's registry of client architecture identifiers is at: + + https://www.iana.org/assignments/dhcpv6-parameters/...

I am using Dovecot 1.2RC2 with Postfix 2.5.5. Everything is running fine. I would like to start using address extensions and have e-mail automatically filtered into folders based on the folder name after the "+" in the e-mail address. I only use system users, no virtual users. I have Deliver configured in main.cf as: mailbox_command = /usr/local/libexec/dovecot/deliver Everything I

...LOADiis TEMP[1].z, [0] This should be: LOAD TEMP[1].z, RINPUT, 0 So I need to add handling to generate the RINPUT here. I'm wondering what the best place is for this. Do I simply intercept the LOAD in LowerMachineInstrToMCInst and add an extra operand there ? >> 5) Talking about the lowecase suffixes to the instructions, >> these should not be part of the output, how do I filter these? >> >> 6) And finally, the current llvm-tgsi output uses e.g. >> TEMP1y where as for the destination it should use TEMP[1].y >> and for the sources it should use TEMP[1].xxxx...

...andled > correctly, I see that the LOAD instructions get postfixed > with a i reps. g for input / global how would I go about > modifying the code emitter (AsmPrinter?) to change "LOADi" > into "LOAD <dest> RINPUT <offset>"? > > 5) Talking about the lowecase suffixes to the instructions, > these should not be part of the output, how do I filter these? > > 6) And finally, the current llvm-tgsi output uses e.g. > TEMP1y where as for the destination it should use TEMP[1].y > and for the sources it should use TEMP[1].xxxx (so include > pr...

...emitter (AsmPrinter?) to change "LOADi" > into "LOAD <dest> RINPUT <offset>"? > I don't understand exactly why you want to change this. Are you trying to make the assembly string for input loads and global loads look the same? > 5) Talking about the lowecase suffixes to the instructions, > these should not be part of the output, how do I filter these? > > 6) And finally, the current llvm-tgsi output uses e.g. > TEMP1y where as for the destination it should use TEMP[1].y > and for the sources it should use TEMP[1].xxxx (so include > p...

Sorry, i come back to this topic in a different thread, because i'm still totally puzzled with the previuous one. Louis, sorry me. ;( I've tried to start with this, that seems very simple: https://wiki.debian.org/NFS/Kerberos And so i've done: a) installed 'nfs-kernel-server' on server, 'nfs-common' on client. Ok, this is easy. b) AFAI've understood i need