similar to: Resurrecting old thread about DNS updates

Displaying 20 results from an estimated 200 matches similar to: "Resurrecting old thread about DNS updates"

2023 Nov 06
1
DNS: Update not allowed for unsigned packet
Thanks Andrew, but we checked for that. Firing up dnsmgmt.msc shows no entries with those computer names. -A On Mon, Nov 6, 2023 at 11:34?AM Andrew Bartlett <abartlet at samba.org> wrote: > On Mon, 2023-11-06 at 10:02 -0800, Aaron C. de Bruyn via samba wrote: > > DNS is suddenly not working properly for some machines. > > > > > > > > We had a bunch of
2012 May 21
3
Resurrecting the old "klibc-cvs" mailing list
I'm thinking I should make a commit robot (like the tip-bot for the Linux kernel) for klibc since development has been picking up again. I could revive the old klibc-cvs mailing list, or make a new one from scratch, or even direct all the commits to the main klibc mailing list. What would people's preference be, here? -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work
2012 Aug 28
2
[LLVMdev] [RFC] Resurrecting the C back-end
I think the C backend also allow people performing source-to-source transform with LLVM (instead of Clang). ether On Tue, Aug 28, 2012 at 10:30 AM, Philipp Klaus Krause <pkk at spth.de> wrote: > Will this allow users to compile C++ (or some other language that LLVM > has a frontend for) to C, which then can be compiled using a C compiler > for a target architecture, for which only
2012 Aug 28
0
[LLVMdev] [RFC] Resurrecting the C back-end
On 8/27/2012 9:57 PM, Hongbin Zheng wrote: > I think the C backend also allow people performing source-to-source > transform with LLVM (instead of Clang). I do not believe that this would be the case nor that it should be a goal. Source-to-source transformation requires a lot of accurate information about the AST, and conversion to LLVM IR is way too lossy. Signedness, for example, is
2012 Aug 28
0
[LLVMdev] [RFC] Resurrecting the C back-end
Hi Roel, It's good to know that you're working on C backend. But IMO, the reason that C backend was removed in LLVM 3.1 is no one maintain the C backend. If you bring it back, would you like to take the responsibility for the maintaining work? Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.)
2012 Aug 28
0
[LLVMdev] [RFC] Resurrecting the C back-end
On 27.08.2012 22:56, Roel Jordans wrote: > > Anyway, that brings to my final question: Which features are > critical/important/wanted/unwanted for a C back-end? > I'd like it to be easy to configure (e.g. to tell which size int is assumed to have). I'd prefer the resulting code to not rely on implementation-defined behaviour (e.g. not make any assumptions about the size of
2012 Feb 16
1
Resurrecting old Splus objects
I have a small file of the type that S-PLUS produced and stored in .Data/ directories back in the days before we used R. I'm fairly sure it would become a dataframe if read into Ver 3.4 of that august predecessor to what we use now. (It was Solaris in case that makes any difference.) AFAIK, the format that S-PLUS uses changed after that, so a current version would find it unreadable. If
2012 Aug 28
0
[LLVMdev] [RFC] Resurrecting the C back-end
On Aug 27, 2012, at 10:39 PM, Philipp Klaus Krause <pkk at spth.de> wrote: > On 28.08.2012 14:08, Joshua Cranmer wrote: >> On 8/27/2012 9:57 PM, Hongbin Zheng wrote: >>> I think the C backend also allow people performing source-to-source >>> transform with LLVM (instead of Clang). >> >> I do not believe that this would be the case nor that it should
2012 Aug 28
1
[LLVMdev] [RFC] Resurrecting the C back-end
On 28.08.2012 14:47, Cameron Zwarich wrote: > On Aug 27, 2012, at 10:39 PM, Philipp Klaus Krause <pkk at spth.de> wrote: > >> On 28.08.2012 14:08, Joshua Cranmer wrote: >>> On 8/27/2012 9:57 PM, Hongbin Zheng wrote: >>>> I think the C backend also allow people performing source-to-source >>>> transform with LLVM (instead of Clang). >>>
2012 Aug 28
1
[LLVMdev] [RFC] Resurrecting the C back-end
On 28/08/12 04:30, Philipp Klaus Krause wrote: > Will this allow users to compile C++ (or some other language that LLVM > has a frontend for) to C, which then can be compiled using a C compiler > for a target architecture, for which only a C compiler exists? > Which use-cases do you have in mind for this backend? > Possibly yes, compiling C++ to C would require support for things
2012 Aug 28
0
[LLVMdev] [RFC] Resurrecting the C back-end
Will this allow users to compile C++ (or some other language that LLVM has a frontend for) to C, which then can be compiled using a C compiler for a target architecture, for which only a C compiler exists? Which use-cases do you have in mind for this backend? Philipp
2012 Aug 28
2
[LLVMdev] [RFC] Resurrecting the C back-end
On 28.08.2012 14:08, Joshua Cranmer wrote: > On 8/27/2012 9:57 PM, Hongbin Zheng wrote: >> I think the C backend also allow people performing source-to-source >> transform with LLVM (instead of Clang). > > I do not believe that this would be the case nor that it should be a > goal. Source-to-source transformation requires a lot of accurate > information about the AST,
2012 Aug 27
9
[LLVMdev] [RFC] Resurrecting the C back-end
Hello all, I am in need for a working C back-end for LLVM for my current research. I know that the previous incarnation of this back-end has been kicked out of the tree since the 3.1 release and I have gone through the archives to restore it to it's previous 'glory'. So far, I have restored most of the previous version (excluding some of the parts that needed changes outside of
2008 Jul 12
1
IMAP Storage Problem
Hi, I'm having a problem with IMAP storage and asterisk. Here is the error message I get (in this instance its checking messages): [Jul 11 23:14:12] WARNING[9888]: app_voicemail.c:8738 mm_log: IMAP Warning: SECURITY PROBLEM: insecure server advertised AUTH=PLAIN [Jul 11 23:14:12] ERROR[9888]: app_voicemail.c:8741 mm_log: IMAP Error: IMAP protocol error: Authentication aborted [Jul 11
2013 Sep 16
1
Fwd: Samba4 DC with multiple IPs
Hi, I installed a samba 4 DC. It works fine, however it autoregisters all IPs in DNS (Dynmaic Update). This bears the problem that when a client wants to connect to the DC it connects using a wrong ip. I tried to remove the IP using dnsmgmt.msc, this works for around an hour than the "wrong" address is back again. Is there a way to limit dynamic updates to a specific interface or can
2019 Jul 18
0
Can't find machine account
On 18/07/2019 16:44, Robert A Wooldridge via samba wrote: > > On 07/18/2019 10:41 AM, Rowland penny via samba wrote: >> >> Anything from here on is nothing to do with your problem, it? is just >> artefacts of the clean up. >> >> It seems to be failing whilst trying to add the 'A' record for your >> new DC. >> >> Lets backtrack a
2019 Jul 18
1
Can't find machine account
On 07/18/2019 11:04 AM, Rowland penny via samba wrote: > On 18/07/2019 16:44, Robert A Wooldridge via samba wrote: >> >> On 07/18/2019 10:41 AM, Rowland penny via samba wrote: >>> >>> Anything from here on is nothing to do with your problem, it is just >>> artefacts of the clean up. >>> >>> It seems to be failing whilst trying to add the
2023 Nov 06
1
DNS: Update not allowed for unsigned packet
On Mon, 2023-11-06 at 10:02 -0800, Aaron C. de Bruyn via samba wrote: > DNS is suddenly not working properly for some machines. > > > > We had a bunch of machines that were joined to the domain, but the > computer > > name was wrong. > > > > To fix this, we unjoined the machines and deleted the computer > accounts out > > of Samba (because
2023 Nov 06
1
DNS: Update not allowed for unsigned packet
DNS is suddenly not working properly for some machines. We had a bunch of machines that were joined to the domain, but the computer name was wrong. To fix this, we unjoined the machines and deleted the computer accounts out of Samba (because renames while joined will leave LDAP attributes with the previous machine name and there will be connectivity problems for some reason), and we deleted them
2019 Jul 18
3
Can't find machine account
On 07/18/2019 10:41 AM, Rowland penny via samba wrote: > > Anything from here on is nothing to do with your problem, it? is just > artefacts of the clean up. > > It seems to be failing whilst trying to add the 'A' record for your > new DC. > > Lets backtrack a little, I asked if the Windows DC was running a dns > server and you answered 'yes'. Lets