Daher schon einmal danke für den Einblick in die Veranstaltung. Gab es denn seitens der Stadtvertreter aussagen bezüglich des weiteren Vorgehens? Was sind die nächsten Schritte? Wie und wo wird nun weiter geprüft und beraten?
Wann soll eine Entscheidung zur Umwidmung getroffen werden? Florian Prinzip: Ja das wird von der Stadtverwaltung gerne herangezogen um die Argumente für das LSG zu zerreden, aber hier geht es um ein Thema dass alle Rostocker angeht. Das LSG ist ein Hauptargument für Touristen Rostock zu besuchen und hier Erholung zu finden.
Dieses Bauvorhaben ist erst der Anfang, wenn der Präzedenzfall genehmigt wird, dann werden die anderen geschützten Gebiete auch fallen. Thanks for the post as well as the clarifications in the comment! will have to dive into upgrading to Nextcloud in the next few days, and to be honest, I was not looking forward to the problems this might bring with it. feel much more at ease now. the migration that way as well and it could have been go badly wrong, but luckily I had a backup so I took that risk. was not sure if I need to do this in Nextcloud as well or not.
find that part of the Nextcloud documentation covering this. Great to read that the update worked at the end. Just one remark for others wo might want to upgrade.
The fix was simply to change the OC version in the config. Instead of tricking your Nextcloud by changing the version in the config. This looks like what happened. Specify specific IP addresses to bind to for UDP requests.
homed host due to rpcbind returning a UDP packet from a different IP address than it was sent to. rpcbind will automatically add 127. RR, you can nothing do about this. RR as small as possible.
is now 30 mins or so, this is a good improvement overall. Not perfect, but fairly ok in my opinion. nice to have script support to fix TLSA records that became wrong because of a cert update I wonder if cached records are a problem. one day and even after you updated your name server a machine trying to send you an email might still use the old record for nearly a whole day and so fail to send the message. see an easy way to fix this. not sure this is robust.
So maybe the only way is to decrease the life time of the TLSA record before the update. work with my setup. So scripting around this issue was really a quick fix. RRs are not working properly as expected.
But for now this script seems to easily fix my problem. investigate the other problem later. have tested even the kernel from unstable, but still the server crashes from time to time. crashing because of some IPv6 routine, so deactivating IPv6 helps. this cannot be the solution for this problem.
Hi Ingo, we also suffer from this bug from time to time. we tried several versions and somehow it suddenly stopped after a crash and NO kernel change. today, the exact same thing happened again. from backports, maybe that helps. crash the dom0 kernel.
Yes, Katharina pushes to hard on the decentralized social networks. not true that diaspora is already dead. If you post interesting stuff, people will start watching it. At the same time, I agree, that there is almost no progress at the code itself. Maybe there are still different aspects that prevent users from joining that communities? is no more attractive in 2016 and people expect a much more comfortable solution to follow interesting topics and their friends. Or maybe all in all the age of social networks just comes to an end?
development need a lot of active devs and people willing to operate and update the plattforms. working, but still beyond their own goals. Reply to: Request for Adoption: Buildd.
past there was some effort from my side for a closer cooperation, but that was turned down by the officials. happen as well, although it would be the best solution to integrate it into the official buildd suite. Reply to: Request for Adoption: Buildd. not using XMPP yet because it loses messages, because messages constantly end up in the wrong devices, and because I end up having partial message history scattered across many devices.
know there are protocol extensions to fix all these things, but there is currently no stable XMPP server that implements them all, and even listing them all is a hard job. easy to deploy the lot? Apparently, we are still not there yet.
Hi, just saw this post on Planet Debian, and I thought I would answer your questions, since nobody else has yet! consider myself quite aware of privacy issues. have a GPG key, used to have a Diaspora node, and still refuse to use Skype.
This February, I decided to give up on most of these privacy attempts. want to work with me because we always have to use that weird thing instead of just Google Hangouts like everyone else. use Google Maps because sjsjsjsjsjsjsjj, and now I look like some weirdo.
So I ended up in the middle of nowhere, metaphorically. re going on about. re having no conversations to begin with! why I gave up. trying to change cultural attitudes toward music production, consumption, and participation.
about to make the leap to Friendica, why should I keep wasting my time there? keep using mine for this. Hope this is helpful for you!
Well, yes, can be a solution of course. domains as much as possible. know if this is still valid or not. honor this standard, right? Thanks for your comments! to the network and allow traffic to one of my other servers.
get all of the kernel oops output, right? days without a crash. Long ago, I built an automation plugin for this cause only. Back then, I was working with storage vendor and my focus was Linux storage.
The thing with storage is, if the kernel bug triggers, even the logs are lost. Network bugs are common. And not to forget Scheduler and Memory bugs too. So your ultimate goal is to have a network channel to pass of the kernel oopses to another box for analysis. ve mentioned, is not taking a bridge interface. That should carry your logs.
You can extend this basic with any framework you like. migration or migrating in the reverse directions seems to work fine. ve not yet been able to capture a crash dump, but my problem also seems to be network related. Well, yes, of course there is more than one way to do this. certs being instantly available to every VM. This was for me the easiest way to achieve this. using proxy_pass in nginx, but as the newly generated cert needs to find its way to puppet anyway it will be a manual process for now.
need a network share. Encrypt and ACME protocol is perfectly fine with HTTP Redirects. requests to a specific location on a central server. and your other hosts periodically check that known location for updates.
so checking the central location every couple of weeks after making sure all is working fine is OK. Was looking into this myself just now. nosudo, which is an improvement, but designed to pause while you carry out some operations manually. and connect to VMs via SSH to do the necessary stuff there? htaccess rewrite rule to it. Reply to: Was man nicht hören möchte. Für eine übersichtliche und kritische Zusammenfassung der Lage und was es insbesondere bedeutet, wenn Griechenland über seine Verhältnisse gelebt haben soll, sei ein nicht mehr ganz brandaktueller Artikel von Prof. Klaus Dörre von der FSU Jena empfohlen.
as a password, will allow them in. altogether, so it either returns the password, or nothing at all. receive mail from hotmail. spent a lot of time to get it working, but without success. The only thing that worked was disabling TLS1. and using other certificates.
signed certificates and disable TLS1. auf Religionen eigentlich vernünftige Politiker wie Volker Beck solche Verbrechen rechtfertigen. Reply to: Bind9 vs. Reply to: Bind9 vs. Howveer, I think that serial dance your are doing is not necessary.
working fine for me. Reply to: Bind9 vs. to run my zone including DNSSEC. it looks like it would without DNSSEC. working beautifully for me. consider alternative though, as I followed a tutorial in a German computer magazine that was written for Bind, which I had already used before. Reply to: Bind9 vs. tested key rollovers with the registrar yet.
would like some automation for the rollovers at the registrar as doing it through a web interface will be time consuming and error prone and that could be ugly. Hidden master with PowerDNS, probably PowerDNS with bind backend to start with and a VPN for zone transfers. nsd for the authoritative servers. Automate the key rollovers to the registrar. And after that my big wishlist item is use my servers to make it a bit easier for others to run DNSSEC. so to get good protection of the private key, I would recommend using an OpenPGP smartcard instead.
Even better is to combine using a smartcard with subkeys, as per the other comment. die bisherige Arbeit der einzelnen Buendnisse und Organisationen besser zu buendeln und zu koordinieren. Die Diskussion auf dem Forum ging schon in die richtige Richtung, aber ich kann verstehen, dass wir derzeit noch Schwierigkeiten haben zu vermitteln, was genau das neue Buendnis sein soll.