search for: hilar

Greetings and salutations Asterisk community, I've been contacted by a man who has generously posted some prompts he commissioned from Allison Smith. If you haven't heard Allison in humor mode, you owe it to yourself to hear this. Joey Lindstrom has decided to place these in the public domain and he's asking Digium to include them in the Asterisk prompts collection. Because he's

When last we saw our hero, er, sysadmin, he'd found that the "noarch" BIOS update was, in fact, a self-extracting .exe file, and he'd extracted it. Finally getting the ok to take the system down, the following hilarity (for small values of hilarity) ensued. First, booting off unetbootin to freedos was fine... except it was try to guess which version - freedos + emm386 + himem, no himem, live CD only, or, finally, "no drivers loaded", which works. It gags on something orders of magnitude larger than...

...o their workplace. I've encountered, several times, when sites relied on extensive use of SSH key managed git access and shattered their deployment systems when the git server got moved and hostkeys were either incorrectly migrated or the IP was a re-used IP of a previously accessed SSH target. Hilarity ensued. This kind of hand-tuning of every deployment rapidly becomes a waste of admin time and serves little purpose without very tight control of the "known_hosts", which can be overridden by local users anyway.

On 10/06/2019 16:04, vincent at cojot.name wrote: > > There is probably some amount of redtape on this but AFAIK it works > fine for me: My RHEL7.6 hypervisors are joined to my AD DC 4.10.4 VMs > through use of realm '(and thus sssd): > > Here's a RHEL7.6 client: > # realm list > ad.lasthome.solace.krynn > ? type: kerberos > ? realm-name:

...'ve encountered, > several times, when sites relied on extensive use of SSH key managed > git access and shattered their deployment systems when the git server > got moved and hostkeys were either incorrectly migrated or the IP was > a re-used IP of a previously accessed SSH target. Hilarity ensued. > This kind of hand-tuning of every deployment rapidly becomes a waste > of admin time and serves little purpose without very tight control of > the "known_hosts", which can be overridden by local users anyway. Are SSH host certificates the solution? -- Sincerely, De...

...> > several times, when sites relied on extensive use of SSH key managed > > git access and shattered their deployment systems when the git server > > got moved and hostkeys were either incorrectly migrated or the IP was > > a re-used IP of a previously accessed SSH target. Hilarity ensued. > > This kind of hand-tuning of every deployment rapidly becomes a waste > > of admin time and serves little purpose without very tight control of > > the "known_hosts", which can be overridden by local users anyway. > > Are SSH host certificates the sol...

...;ve done > some extra work, it won't include the eatures to provide a full domain > controller because the gnutls won't be recent enough. And it won't > replace any of the compiled RHEL 7 based libraries with the updated > talloc, tdb, tevent, or ldb libraries. Unpredictable hilarity may > ensue if you expect various features to work consistently, especially > if you weren't very careful to segregate your built Samba from the > default samba libraries built into RHEL 7 and CentOS 7. > > The URL's I published include all the hooks for integrating your n...

Hi, I tried to do live migration from machine A to B. After the migration, machine A still had the record of the VM, though the VM was not running any more. Also, if I shut down the VM on machine B, its record on B would be gone --- I could not see it using "xm list" anymore. However, I can still start the VM on machine A using "xm start". Looks like the migration just move

Hi Gabriel, I've compiled Samba 4.10.2 on CentOS 7 successfully. I've read the wiki that 4.10.2 version is full compatible with python 3, specifically python 3.4. Then I've install, use the yum command, the package python34-devel and I've added an environment variable at /etc/profile with export PYTHON=python3.4. Thus, I've run ./configure, make and make install with no

Hi, using btrfs with LVM snapshots seems to be confusing /proc/mounts After mounting a snapshot of an original filesystem, the devicename of the original filesystem is overwritten with that of the snapshot in /proc/mounts. Steps to reproduce: arnd@kallisto:/mnt$ sudo mount /dev/vg0/original /mnt/original [ 107.041432] device fsid 5c3e8ca2-da56-4ade-9fef-103a6a8a70c2 devid 1 transid 4

...-linux-gnu will work when compiling with gcc, but llvm-gcc will try to feed 64-bit machine code to the assembler in this situation. At least that's what happens when bootstrapping. 4) I also dimly recall having seen llvm-gcc use 64-bit library paths for linking the 32-bit binaries (with ensuing hilarity, of course). I had postponed further investigation with this issue until after I'd get the assembly stage working - this approach had worked well with gcc, too. I'm under the impression that problems 1-3 are caused by autoconf as used in LLVM. I don't know about problem 4; it might...

...tending any wedding affair. All weddings are understood as time for enjoyment. The joining of two hearts by means of wedding rituals also implies the unification of two families. And so, the best way to make the wedding a lot more special is presenting a father of the groom speech and toast full of hilarity and substance! I am positive that useful tips will get you started on the correct path: How to Compose a Father of the groom speech and toast with the Right Quantity of Humor If you're having a hard time being funny, be natural. Avoid putting in too much effort to make a hilarious father of...

...help is available by typing NET HELPMSG 2140. > > > C:\Documents and Settings\antgel>net helpmsg 2140 > > An internal Windows 2000 error occurred. > > EXPLANATION > > A software error occurred. > > ACTION > > Contact technical support. > Aside from the hilarity of the above, I need to get this going, and I am technical support, DOH! This happens from more than one workstation. The strange thing is that it does sometimes work (rarely), but appears to be totally random. I'd appreciate a CC as I'm not subscribed. A -- Now playing: The Mahavish...

Hello, I recently upgraded to openssh 6.6 version and I am finding public authentication doesn't seem to work. I see the openssh application exits with the error, fatal: key_free: bad key type 1515870810 After I created one more user, it throws the below error and exits. fatal: restore_uid: temporarily use_uid not effective I was able to successfully authenticate using 5.x openssh

We uograded our dovecot from version 2.1.10 -> 2.10.12, but within the first hour of use, dovecot-lda would segfault during delivery. This left a lock file lying around causing the user's mail readers to hang; much hilarity ensues. All further deliveries to the same user will result in a crash. The only thing that fixes this condition is to blow away the user's INBOX cache index. Reindexing with "doveadm index" does not fix anything. I've installed a test version with one user's problemati...

...ich has all sorts of horrible thread safety issues. Again, see perlcall(3) for the details. (4) guestfs_close can be called from exit (via an atexit handler) and it's not at all clear that the Perl interpreter won't have been shut down by the time we try to invoke the closure, resulting in hilarity. Since it's now possible to store user data in the Perl handle, I suggest pursuing a Perl-based solution to all this. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or ov...

...tely, unless you've done some extra work, it won't include the eatures to provide a full domain controller because the gnutls won't be recent enough. And it won't replace any of the compiled RHEL 7 based libraries with the updated talloc, tdb, tevent, or ldb libraries. Unpredictable hilarity may ensue if you expect various features to work consistently, especially if you weren't very careful to segregate your built Samba from the default samba libraries built into RHEL 7 and CentOS 7. The URL's I published include all the hooks for integrating your new Samba services as RPM...

...I mean *everything*. Its configuration supports structures that only search "onelevel" in an LDAP directory, but when designating this it precaches the entire LDAP directory containing the "onelevel" objects at startup time, with no way I ever found to turn off this misfeature. Hilarity ensues if if your LDAP server, whether Samba or AD, are not close enough to the clien thost. And if your LDAP is big, that local cache gets *bulky*, even if the "onelevel" published objects only contain one element Now, some of that may be an organizatonal issue, but it surprised the h...

On May 12, 2008, at 10:42 PM, Joachim Durchholz wrote: > The concrete problem is that Ubuntu's way of doing cross compilations > seems incompatible with LLVM's way of using the autoconf machinery. > I've been told that this is Ubuntu's fault, but I'm sceptical: I have > seen LLVM's autoconf do things that autoconf shouldn't do if properly > set up. >

On Thu, Apr 12, 2018 at 6:29 PM, Josh Soref <jsoref at gmail.com> wrote: > Randall S. Becker <rsbecker at nexbridge.com> wrote: > >> >> -REGRESSTMP = "$(PWD)/regress" >> +REGRESSTMP = `pwd` >> >> tests interop-tests t-exec unit: regress-prep regress-binaries $(TARGETS) >> > > It looks like the problem is that pwd is in