Re: auto restarting in crontab

2023-03-17 Thread debian-user
"p...@ymail.ne.jp" wrote: > debian-u...@howorth.org.uk wrote: > > But it sounds like what...@ymail.ne.jp is doing isn't best practice > > either, although I don't fully understand what they mean by "I often > > change default ruby in interactive shell". If they mean 'global' > > then I suspect

Re: auto restarting in crontab

2023-03-17 Thread Nicolas George
debian-u...@howorth.org.uk (12023-03-17): > Please don't send me an individual copy of emails; I am subscribed. Nobody can remember who is subscribed and who is not: do not write this in your mail, write it in the headers, just like I did. -- Nicolas George

Re: auto restarting in crontab

2023-03-17 Thread debian-user
Please don't send me an individual copy of emails; I am subscribed. Dan Ritter wrote: > debian-u...@howorth.org.uk wrote: > > Dan Ritter wrote: > > > p...@ymail.ne.jp wrote: > > > > For dev stuff, for example, I have many versions of ruby > > > > installed in the system by rbenv. > > >

Re: auto restarting in crontab

2023-03-16 Thread Greg Wooledge
On Fri, Mar 17, 2023 at 08:04:24AM +0800, p...@ymail.ne.jp wrote: > Sometimes I was using the older ruby version (1.x), but sometimes I am using > the latest ruby (3.x). For example, different streaming libraries for ruby > require different versions. > > For instance, I developed a ruby client

Re: auto restarting in crontab

2023-03-16 Thread p...@ymail.ne.jp
debian-u...@howorth.org.uk wrote: But it sounds like what...@ymail.ne.jp is doing isn't best practice either, although I don't fully understand what they mean by "I often change default ruby in interactive shell". If they mean 'global' then I suspect they should be using 'local' instead. Or

Re: auto restarting in crontab

2023-03-16 Thread Jeffrey Walton
On Thu, Mar 16, 2023 at 7:03 PM Dan Ritter wrote: > > debian-u...@howorth.org.uk wrote: > > Dan Ritter wrote: > > > p...@ymail.ne.jp wrote: > > > > For dev stuff, for example, I have many versions of ruby installed > > > > in the system by rbenv. > > > > > > > > Since I often change default ruby

Re: auto restarting in crontab

2023-03-16 Thread Dan Ritter
debian-u...@howorth.org.uk wrote: > Dan Ritter wrote: > > p...@ymail.ne.jp wrote: > > > For dev stuff, for example, I have many versions of ruby installed > > > in the system by rbenv. > > > > > > Since I often change default ruby in interactive shell, this may > > > break the ruby for

Re: auto restarting in crontab

2023-03-16 Thread debian-user
Dan Ritter wrote: > p...@ymail.ne.jp wrote: > > For dev stuff, for example, I have many versions of ruby installed > > in the system by rbenv. > > > > Since I often change default ruby in interactive shell, this may > > break the ruby for sysadmin job in crontab. What’s the solution for > >

Re: auto restarting in crontab

2023-03-16 Thread Jude DaShiell
I tried installing task-lxqt-desktop using apt and that didn't go well at all. Since I use a screen reader I ended up installing bullseye mate with the installation disc then upgrading to bookworm. That worked. So far as I can tell, a11y work was not done on lxqt to bring up orca if speakup got

Re: auto restarting in crontab

2023-03-16 Thread Dan Ritter
p...@ymail.ne.jp wrote: > For dev stuff, for example, I have many versions of ruby installed in the > system by rbenv. > > Since I often change default ruby in interactive shell, this may break the > ruby for sysadmin job in crontab. What’s the solution for this? Everywhere it matters, set

Re: Re: auto restarting in crontab

2023-03-16 Thread pyh
For dev stuff, for example, I have many versions of ruby installed in the system by rbenv. Since I often change default ruby in interactive shell, this may break the ruby for sysadmin job in crontab. What’s the solution for this?

Re: auto restarting in crontab

2023-03-16 Thread Nicolas George
Greg Wooledge (12023-03-16): > So they installed > parallel toolsets (commands including ps, echo, and so on) in two > different directories. Four: there is also /usr/xpg4/bin and /usr/xpg6/bin. Regards, -- Nicolas George

Re: auto restarting in crontab

2023-03-16 Thread Greg Wooledge
On Thu, Mar 16, 2023 at 01:57:26PM +0100, Christoph Brinkhaus wrote: > I think you are right. The only remaining argument for specifying the > complete path I have read about is as below. > There might be the situation with different binaries but similar > names. For example /usr/bin/nc is

Re: auto restarting in crontab

2023-03-16 Thread Christoph Brinkhaus
Am Thu, Mar 16, 2023 at 07:27:22AM -0400 schrieb Greg Wooledge: > On Thu, Mar 16, 2023 at 12:24:10PM +0100, Christoph Brinkhaus wrote: > > The environments of login shells and crontab can be different. This > > includes the path where to seek executables. Therefore it is good > > practice not to

Re: auto restarting in crontab

2023-03-16 Thread Greg Wooledge
On Thu, Mar 16, 2023 at 12:24:10PM +0100, Christoph Brinkhaus wrote: > The environments of login shells and crontab can be different. This > includes the path where to seek executables. Therefore it is good > practice not to write just the name of the executable as nc but the > name with the path

Re: auto restarting in crontab

2023-03-16 Thread Christoph Brinkhaus
Am Thu, Mar 16, 2023 at 08:55:54AM +0800 schrieb cor...@free.fr: > Greetings, > > My script for monitoring Node.js app as follows. I put it in crontab for > auto-check and restart if failure. > > #!/bin/bash > > # scan the port > nc -z 127.0.0.1 3000 > > if [ $? -eq 0 ];then > exit > else >

Re: auto restarting in crontab

2023-03-16 Thread Nicolas George
Greg Wooledge (12023-03-16): > That assumes you want to detach the process from its session in the > first place. It's NOT what you should do when running a managed > service, though. > > With a managed service, you don't want ANY of the old legacy "I want > to run a daemon from an interactive

Re: auto restarting in crontab

2023-03-16 Thread Greg Wooledge
On Thu, Mar 16, 2023 at 08:53:55AM +0100, Nicolas George wrote: > cor...@free.fr (12023-03-16): > > nohup serve -s /home/myUsername/workspace/xxx-frontend/build & > > What Greg said. Plus: > > Never use nohup. nohup should never have been invented, it is based on a > complete lack of

Re: auto restarting in crontab

2023-03-16 Thread Nicolas George
cor...@free.fr (12023-03-16): > nohup serve -s /home/myUsername/workspace/xxx-frontend/build & What Greg said. Plus: Never use nohup. nohup should never have been invented, it is based on a complete lack of understanding of how sessions and control terminal work. Instead: - use setsid to

Re: auto restarting in crontab

2023-03-16 Thread coreyh
updated: Thanks for all your helps, especially @Greg and @Yong Now this systemd service has been enabled and just works. I put a file on /etc/systemd/system/xxx.service whose content as, [Unit] Description=xxx Front After=network.target [Service] Type=simple Restart=always RestartSec=5

Re: auto restarting in crontab

2023-03-15 Thread Jeremy Ardley
On 16/3/23 12:09, p...@ymail.ne.jp wrote: Just for fun, I asked this question on ChatGPT, who gives the answers as follows. Q:  Please help generate a systemd configuration for Debian linux A: Sure, here's an example of a systemd configuration file for a Debian Linux service: Be very

Re: auto restarting in crontab

2023-03-15 Thread p...@ymail.ne.jp
Just for fun, I asked this question on ChatGPT, who gives the answers as follows. Q: Please help generate a systemd configuration for Debian linux A: Sure, here's an example of a systemd configuration file for a Debian Linux service: ``` [Unit] Description=My Service After=network.target

Re: auto restarting in crontab

2023-03-15 Thread p...@ymail.ne.jp
cor...@free.fr wrote: where will I setup this script for systemd job? any reference? You might look at this article as well. https://linuxhandbook.com/create-systemd-services/ Yong

Re: auto restarting in crontab

2023-03-15 Thread Greg Wooledge
On Thu, Mar 16, 2023 at 09:40:48AM +0800, cor...@free.fr wrote: > On 16/03/2023 09:32, Greg Wooledge wrote: > > If that's more than you want to tackle, and if all you want is > > automatic restarting (not the ability to stop it at will), then this > > should suffice: > > > > #!/bin/sh > >

Re: auto restarting in crontab

2023-03-15 Thread coreyh
On 16/03/2023 09:32, Greg Wooledge wrote: On Wed, Mar 15, 2023 at 08:00:20PM -0500, Nicholas Geovanis wrote: On Wed, Mar 15, 2023, 7:56 PM wrote: > My script for monitoring Node.js app as follows. I put it in crontab for > auto-check and restart if failure. There's so much wrong with that.

Re: auto restarting in crontab

2023-03-15 Thread Greg Wooledge
On Wed, Mar 15, 2023 at 08:00:20PM -0500, Nicholas Geovanis wrote: > On Wed, Mar 15, 2023, 7:56 PM wrote: > > My script for monitoring Node.js app as follows. I put it in crontab for > > auto-check and restart if failure. There's so much wrong with that. If you want to manage a service, the

Re: auto restarting in crontab

2023-03-15 Thread Nicholas Geovanis
On Wed, Mar 15, 2023, 7:56 PM wrote: > Greetings, > > My script for monitoring Node.js app as follows. I put it in crontab for > auto-check and restart if failure. > > #!/bin/bash > > # scan the port > nc -z 127.0.0.1 3000 > > if [ $? -eq 0 ];then >exit > else >killall node >sleep 1