Styjun

pgfplots: How to draw a tangent graph below two others?

How does a dynamic QR code work?

Why do we say “un seul M” and not “une seule M” even though M is a “consonne”?

Could a dragon use its wings to swim?

Raspberry pi 3 B with Ubuntu 18.04 server arm64: what pi version

What steps are necessary to read a Modern SSD in Medieval Europe?

How can the PCs determine if an item is a phylactery?

Is it possible to make a 9x9 table fit within the default margins?

MT "will strike" & LXX "will watch carefully" (Gen 3:15)?

What does this strange code stamp on my passport mean?

Finitely generated matrix groups whose eigenvalues are all algebraic

Avoiding the "not like other girls" trope?

What happens if you break a law in another country outside of that country?

Is it a bad idea to plug the other end of ESD strap to wall ground?

Does Germany produce more waste than the US?

Why did early computer designers eschew integers?

Why doesn't Shulchan Aruch include the laws of destroying fruit trees?

How exploitable/balanced is this homebrew spell: Spell Permanency?

Ising model simulation

Small nick on power cord from an electric alarm clock, and copper wiring exposed but intact

How should I connect my cat5 cable to connectors having an orange-green line?

How can a day be of 24 hours?

Creating a script with console commands

Gauss' Posthumous Publications?

Any way to tell .profile.bashrc that script is already running?

0

I was wondering if there is any argument that I can add to my bash script so it won't be executed again on log on, because it' already executed on reboot. That causes the script to stop, when runned second time.

Bash:

if [ "$BASH" ]; then
 if [ -f ~/.bashrc ]; then
 . ~/.bashrc
 fi
fi

mesg n || true

cd /root/Boti/Gianni/
bash /root/Boti/Gianni/comanda.sh

I am using Debian 9 on a VPS.

bash

share|improve this question

asked Mar 21 at 19:59

DalacDalac

33

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Does your /tmp directory get cleared on reboot? What do you want to do if the script has exited and you run it again?
  
  – jhnc
  Mar 21 at 21:28
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It is running in the background with nohup. I just want bash to recognize that it's already running and not execute it everytime I log on.
  
  – Dalac
  Mar 21 at 21:32
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  So you don't care if it dies unexpectedly for some reason? You'll just wait until the next reboot to restart it? (Not rhetorical. It changes the answer.) And does your /tmp directory get cleaned on reboot?
  
  – jhnc
  Mar 21 at 21:44
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The VPS has an 99,98% uptime. I'm not worried for that. And yes, my /tmp it's empty after every reboot.
  
  – Dalac
  Mar 21 at 23:28
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I was asking about comanda.sh dying, not the VPS being unreliable. mkdir /tmp/comanda.lock || exit at start of comanda.sh guarantes only one invocation per boot or until the directory is deleted by some other means. Can probably use /run/lock/comanda.lock instead.
  
  – jhnc
  Mar 21 at 23:41
  

  
  
  
  

add a comment | 

0

I was wondering if there is any argument that I can add to my bash script so it won't be executed again on log on, because it' already executed on reboot. That causes the script to stop, when runned second time.

Bash:

if [ "$BASH" ]; then
 if [ -f ~/.bashrc ]; then
 . ~/.bashrc
 fi
fi

mesg n || true

cd /root/Boti/Gianni/
bash /root/Boti/Gianni/comanda.sh

I am using Debian 9 on a VPS.

bash

share|improve this question

asked Mar 21 at 19:59

DalacDalac

33

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Does your /tmp directory get cleared on reboot? What do you want to do if the script has exited and you run it again?
  
  – jhnc
  Mar 21 at 21:28
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It is running in the background with nohup. I just want bash to recognize that it's already running and not execute it everytime I log on.
  
  – Dalac
  Mar 21 at 21:32
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  So you don't care if it dies unexpectedly for some reason? You'll just wait until the next reboot to restart it? (Not rhetorical. It changes the answer.) And does your /tmp directory get cleaned on reboot?
  
  – jhnc
  Mar 21 at 21:44
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The VPS has an 99,98% uptime. I'm not worried for that. And yes, my /tmp it's empty after every reboot.
  
  – Dalac
  Mar 21 at 23:28
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I was asking about comanda.sh dying, not the VPS being unreliable. mkdir /tmp/comanda.lock || exit at start of comanda.sh guarantes only one invocation per boot or until the directory is deleted by some other means. Can probably use /run/lock/comanda.lock instead.
  
  – jhnc
  Mar 21 at 23:41
  

  
  
  
  

add a comment | 

I was wondering if there is any argument that I can add to my bash script so it won't be executed again on log on, because it' already executed on reboot. That causes the script to stop, when runned second time.

Bash:

if [ "$BASH" ]; then
 if [ -f ~/.bashrc ]; then
 . ~/.bashrc
 fi
fi

mesg n || true

cd /root/Boti/Gianni/
bash /root/Boti/Gianni/comanda.sh

I am using Debian 9 on a VPS.

bash

share|improve this question

asked Mar 21 at 19:59

DalacDalac

33

if [ "$BASH" ]; then
 if [ -f ~/.bashrc ]; then
 . ~/.bashrc
 fi
fi

mesg n || true

cd /root/Boti/Gianni/
bash /root/Boti/Gianni/comanda.sh

share|improve this question

asked Mar 21 at 19:59

DalacDalac

33

share|improve this question

asked Mar 21 at 19:59

DalacDalac

33

asked Mar 21 at 19:59

DalacDalac

33

asked Mar 21 at 19:59

DalacDalac

33