Tor service not working every time I restart, saying active (exited) [on hold]

I am trying to run the tor service on a Debian Stretch machine, and it works intermittently. However, after every successful start, upon the time I try to start it again, it doesn’t work. When I run “systemctl status tor” it says “active (exited)”. I’d post the entire error log, but sadly it is on a virtual machine. What is causing this, and how can I fix it so that every time I start the service it works as it should?

Tor service says “active (exited)”

I am trying to run the tor service on a Debian Stretch machine, and it works intermittently. However, after every successful start, upon the time I try to start it again, it doesn’t work. When I run “systemctl status tor” it says “active (exited)”. I’d post the entire error log, but sadly it is on a virtual machine. I don’t know how relevant this is, but I’m also running Nginx, and Tor is being run for the purpose of hidden service hosting. What is causing this, and how can I fix it so that every time I start the service it works as it should?

¿Cómo crear un trigger que actualice el stock y además active un valor booleano si se está debajo o sobre el valor del stock mínimo?

introducir la descripción de la imagen aquí

Tengo este trigger no me genera error al crearlo, pero al insertar en la tabla detalle_entrada genera un error de tabla producto desconocida.

DELIMITER $  $       CREATE DEFINER = CURRENT_USER TRIGGER proyectofinaldae.entrada     AFTER INSERT ON detalle_entrada FOR EACH ROW     BEGIN     Update PRODUCTO     set PRODUCTO.STOCK = PRODUCTO.STOCK + NEW.cantidad     where PRODUCTO.ID_PRODUCTO = NEW.ID_PRODUCTO;         IF PRODUCTO.STOCK > producto.stock_minimo THEN BEGIN             UPDATE producto set producto.aviso_stock_minimo=false where PRODUCTO.ID_PRODUCTO = NEW.ID_PRODUCTO;         END;          ELSEIF PRODUCTO.STOCK < producto.stock_minimo THEN BEGIN             UPDATE producto set producto.aviso_stock_minimo=true where PRODUCTO.ID_PRODUCTO = NEW.ID_PRODUCTO;         END;         END IF;     END$  $       DELIMITER ; 

Can Android stay in doze mode even with an active screen in last Android version?

First of all, sorry if this question doesn’t belong here, I wanted to ask on meta if I coudld answer this, but I’m unable to. Anyway I think it fits more here than in stackoverflow. If it’s not the case, I’ll move it there.

Point is that I’m developing an Android app and on the Android emulator with Android Pie version, it happens that, once I get to run some Android services from my app the terminal seems to block any services that might happen later.

I’ve checked that this is due to that the emulator enters doze mode once those first services are run, as if I make the needed operation to bypass the mode (allowing full use of the battery to my app, as also seen in the same page I’m previously linking), then the services are run with no problems.

What I find very strange is that even when the user is using the phone that doze mode is happening, seemingly the whole time until device restarts, so I wonder is this might be some type of emulator bug.

To answer this question it just would be needed that someone would check in a physical device with Android Pie, if a service run by some app always executes with the device being active, without having done the mentioned change in app’s battery management, or find the documentation that explicitly defines this (I’m not able to).