can you combine that: https://www.gambas-es.org/viewtopic.php?f=5&t=6396
with a combination of some of that tools:
a) recursive programing or exec callback's (i really not expert in this
with gambas)
b) http://cr.yp.to/daemontools.html
c) http://supervisord.org/
Lenz McKAY Gerardo (PICCORO)
http:/
Peace,
Can gbr3 be made to log fatal interpreter errors to file?
Thanks!
--
View this message in context:
http://gambas.8142.n7.nabble.com/Logging-errors-in-apps-running-as-Application-Daemon-tp59450p59565.html
Sent from the gambas-user mailing list archive at Nabble.com.
-
Peace!
Making apps daemons is exactly what I want to achieve, but couldn't get
interpreter errors to log to file in native daemon mode. So I thought maybe
a wrapper can start a non daemon app, intercept all output including
interpreter errors, and go into background?
This is boot time start "se
On Thu, 22 Jun 2017, alexchernoff wrote:
> Anyone know if there is a wrapper to daemonize apps while keeping them in
> regular console mode? That way maybe it will be possible to log fatal
> interpreter errors?
>
Why do you want to daemonise then? From the manpage of daemon():
The daemon() fun
Anyone know if there is a wrapper to daemonize apps while keeping them in
regular console mode? That way maybe it will be possible to log fatal
interpreter errors?
Peace!
--
View this message in context:
http://gambas.8142.n7.nabble.com/Logging-errors-in-apps-running-as-Application-Daemon-tp
well, at least system.backtrace[1] (or error.backtrace[0] seem to show the
error line.
But it would be nice to get fatal interpreter errors written to a file.
cheers!
--
View this message in context:
http://gambas.8142.n7.nabble.com/Logging-errors-in-apps-running-as-Application-Daemon-tp594
Le 22/06/2017 à 13:56, alexchernoff a écrit :
Peace!
Well, Public Sub Application_Error() does fire upon a fatal error, but is it
possible to know what the last error was?
cheers!
At the moment, no.
--
Benoît Minisini
---
Peace!
Well, Public Sub Application_Error() does fire upon a fatal error, but is it
possible to know what the last error was?
cheers!
--
View this message in context:
http://gambas.8142.n7.nabble.com/Logging-errors-in-apps-running-as-Application-Daemon-tp59450p59502.html
Sent from the gamba
On Wed, 21 Jun 2017 13:51:11 +0200
Tobias Boege wrote:
> On Wed, 21 Jun 2017, adamn...@gmail.com wrote:
> > On Wed, 21 Jun 2017 02:17:27 -0700 (MST)
> > alexchernoff wrote:
> >
> > > Peace to all,
> > >
> > > I have some Gb projects that are in Application.Daemon mode. But sometimes
> > > if p
in the case of deamon redirection, for those using Devuan, Debian and
VenenuX the correct way to always see what happened to their daemons
process it to strting run by the command "start-stop-daemon" as good choice
with proper flags to redirect output...
this will heppl to redirect the ouptu and s
On Wed, 21 Jun 2017, Tobias Boege wrote:
> Attached are two scripts
--
"There's an old saying: Don't change anything... ever!" -- Mr. Monk
#!/usr/bin/gbs3
Public Sub Main()
Print "a"
Application.Daemon = True
Wait 0.1 ' ensure we daemon'd(?)
Print "b"
Print 1 / 0
Print "c"
End
#!/usr
On Wed, 21 Jun 2017, adamn...@gmail.com wrote:
> On Wed, 21 Jun 2017 02:17:27 -0700 (MST)
> alexchernoff wrote:
>
> > Peace to all,
> >
> > I have some Gb projects that are in Application.Daemon mode. But sometimes
> > if process dies for whatever reason, I can't see what the last error was. I
>
On Wed, 21 Jun 2017 02:17:27 -0700 (MST)
alexchernoff wrote:
> Peace to all,
>
> I have some Gb projects that are in Application.Daemon mode. But sometimes
> if process dies for whatever reason, I can't see what the last error was. I
> have to run it in a console without daemonizing and wait for
On Wed, 21 Jun 2017 02:17:27 -0700 (MST)
alexchernoff wrote:
> Peace to all,
>
> I have some Gb projects that are in Application.Daemon mode. But sometimes
> if process dies for whatever reason, I can't see what the last error was. I
> have to run it in a console without daemonizing and wait for
Peace to all,
I have some Gb projects that are in Application.Daemon mode. But sometimes
if process dies for whatever reason, I can't see what the last error was. I
have to run it in a console without daemonizing and wait for it to die and
show last reason (like "#13: Null object" or something).
15 matches
Mail list logo
