We are using Weston, we started Weston as service and added that dependency
to hmi application.
Iam starting as user service.
There is no reason for starting as basic.target. For testing purpose , iam
using basic.target.
I don't think so, it depends on any hardware. As of my understanding only
On Wed, 2018-08-29 at 19:49 +0200, Cecil Westerhof wrote:
> There are a lot of ways you can select the output you get from
> journalctl, but it seems you cannot select on the message itself.
> That is why I need to do something like:
> journalctl | grep 'Database is locked'
>
> Is this true,
There are a lot of ways you can select the output you get from journalctl,
but it seems you cannot select on the message itself. That is why I need to
do something like:
journalctl | grep 'Database is locked'
Is this true, or am I overlooking something?
--
Cecil Westerhof
On 29 August 2018 at 16:14, Wojtek Swiatek wrote:
> Le mer. 29 août 2018 à 17:11, Steve Dodd a écrit :
>> Shouldn't be that hard to adapt one of the above for nspawn?
> nspawn is not the problem - portable services are. I use a minimal image
> with nspawn which is OK but portable services are
Le mer. 29 août 2018 à 17:11, Steve Dodd a écrit :
> On 29 August 2018 at 15:43, Steve Dodd wrote:
>
> Shouldn't be that hard to adapt one of the above for nspawn?
>
>
nspawn is not the problem - portable services are. I use a minimal image
with nspawn which is OK but portable services are
On 29 August 2018 at 15:43, Steve Dodd wrote:
> I'm kind of surprised a tool for this hasn't crossed my path already, [..] I
> also wonder if there might be any
> Docker based tools that do this sort of inspection.
Bingo:
- https://github.com/djosephsen/skinnywhale/blob/master/skinnywhale.sh
On 29 August 2018 at 11:24, Wojtek Swiatek wrote:
[..]
> How should I create a filesystem which has only the files required by the
> packages (= the ones it brings in, as well as all the dependencies)?
This is a good question and one which is on my list of things to look
at soon for various
Does your application report any errors after failed startup?
How is the "touch feature" implemented? Does it depend on any services, any
hardware devices?
Are you starting the application as a system service, or as a --user
service?
Why are you using basic.target?
On Wed, Aug 29, 2018 at 3:55
Hi,
I have a hmi application(without touch feature enabled) created using cgi.
If I start that application under basic.target, it's running successfully.
But if I start that application( with touch enabled) under basic.target it
is failing to start.
Even systemctl --user start hmi.service also
I know that this is not the usual answer to that sort of question but
you should try buildroot, rather than base yourself on debian.
When you deactivate the kernel and busybox (it's done through a
menuconfig type interface) you will get the minimal type of system you want.
On
Hello everyone,
v239 brought in portable services (a good description is at
http://0pointer.net/blog/walkthrough-for-portable-services.html) and while
I still cannot make it work (I do not have a /usr/lib/systemd/portablectl
despite having systemd --version reporting 239, but this is going to be
On Wed, 29 Aug 2018, Wojtek Swiatek wrote:
> Le mer. 29 août 2018 à 10:03, Michael Chapman a
> écrit :
>
> Thank you for the clarification.
>
>
> > > Question 2: how can I configure the prog_two/prog_three case, i.e. having
> > > them starting one after the other (= start prog_three when
Le mer. 29 août 2018 à 10:03, Michael Chapman a
écrit :
Thank you for the clarification.
> > Question 2: how can I configure the prog_two/prog_three case, i.e. having
> > them starting one after the other (= start prog_three when prog_two is
> > done), and have the prompt return immediately
>
On Wed, 29 Aug 2018, Wojtek Swiatek wrote:
> Hello everyone
>
> systemctl start myserv.service sometimes immediately returns to the shell
> prompt and sometimes stays until the program is done. Specifically, taking
> the example of two programs
>
> - prog_one which starts in the foreground and
Hello everyone
systemctl start myserv.service sometimes immediately returns to the shell
prompt and sometimes stays until the program is done. Specifically, taking
the example of two programs
- prog_one which starts in the foreground and never ends, defined as
ExecStart=/path/to/prog_one
-
15 matches
Mail list logo
