search for: vps2

...zeof(linenovar)-7, "%d", lineno); } +#endif return strchrnul(v->text, '=') + 1; } return NULL; diff --git a/usr/dash/var.h b/usr/dash/var.h index 4c02eb2..1a06a3c 100644 --- a/usr/dash/var.h +++ b/usr/dash/var.h @@ -88,9 +88,15 @@ extern struct var varinit[]; #define vps2 (&vps1)[1] #define vps4 (&vps2)[1] #define voptind (&vps4)[1] +#ifdef WITH_LINENO #define vlineno (&voptind)[1] +#endif #ifndef SMALL +#ifdef WITH_LINENO #define vterm (&vlineno)[1] +#else +#define vterm (&voptind)[1] +#endif #define vhistsize (&vterm)[1] #endif

Hi, I have a question around whether there is any way to control tinc routing if you have multiple routes to the same destination. I have a three node configuration, let's call them: home -> connects to both other nodes vps1 -> a VPS, providing connection to the internet vps2 -> another VPS, also providing a connection to the internet Both vps nodes provide their own 192.168.x.0 subnet as well as 0.0.0.0/0 to allow any traffic to go that way and out to the internet (via SNAT.) My original plan was to have different weightings on the 0.0.0.0/0 networks so that I got...

I have a VPS running C7. I ran a 'yum update' which included a kernel update. The yum update wasn't a total success because mariadb updates failed. However everything else appeared to work. However, when I rebooted the server it did not restart. I have managed to get the ISP's support desk to boot the server by selecting the previous kernel, and I now have access to my box again.

...ave managed to find out what happened in the yum update and it turns out it was a mess. It looks like the server ran out of memory in the middle and things then started to fail. Any advice on how to recover from this would be greatly appreciated > > The log below shows: > > [root at vps2 ~]# yum history info 22 > Loaded plugins: fastestmirror, langpacks > Repository mariadb is listed more than once in the configuration > Transaction ID : 22 > Begin time : Sun Jan 19 18:15:33 2020 > Begin rpmdb : 795:6c5cd82e3ada047c7071fea1524f41fd13fab6a1 > End time...

I have managed to find out what happened in the yum update and it turns out it was a mess. It looks like the server ran out of memory in the middle and things then started to fail. Any advice on how to recover from this would be greatly appreciated The log below shows: [root at vps2 ~]# yum history info 22 Loaded plugins: fastestmirror, langpacks Repository mariadb is listed more than once in the configuration Transaction ID : 22 Begin time : Sun Jan 19 18:15:33 2020 Begin rpmdb : 795:6c5cd82e3ada047c7071fea1524f41fd13fab6a1 End time : 19:19:32 2020 (63...

...the yum update and it turns >> out it was a mess. It looks like the server ran out of memory in the >> middle and things then started to fail. Any advice on how to recover >> from this would be greatly appreciated >> >> The log below shows: >> >> [root at vps2 ~]# yum history info 22 >> Loaded plugins: fastestmirror, langpacks >> Repository mariadb is listed more than once in the configuration >> Transaction ID : 22 >> Begin time : Sun Jan 19 18:15:33 2020 >> Begin rpmdb : 795:6c5cd82e3ada047c7071fea1524f41fd13fab6a1...