When i run my app via immortal with yml config, if i don't specify the log option, i don't see any logs in my console, apart from process starts and exists. Is it possible to have the logs sent to the console from a running process?

Hi ! I'm using immortal with Linux Mint and the SSTV software since this program is buggy and exit itself whenever while it must receive SSTV pictures from ISS. So in order to avoid missing pictures from the International Space Station, Immortal is a must have software. I've just installed QSSTV on my raspberry and I didn't find any package for Raspbian and ARM device working for my Raspbian under Raspberry. I've passed many hours to try to compile the software but I never succeed.

So can someone help me to get a working package or un very good tutorial about how to compile this software for my raspberry ? New pictures are being sent this week-end from ISS...

Many thanks to all people who will help me.

David.

This PR makes the processes started directly with immortal addressible by the service name as derived from the config filename. This mirrors the behaviour of immortaldir. I have a use case where I need to use the require directive for monitored processes which are not started by immortaldir but directly by immortal itself. Currently such process have the PID as name. This makes using require impossible. Feedback appreciated.

To further elaborate on the use case. We are using this modified version of immortal in combination with https://github.com/Supervisor/supervisor which has pretty clumsy dependency support. Immortal solves this in a very simple in effective manner. Reason for using supervisor is that we can, at this time, better control the stdout/stderr redirection for monitored processes inside container environments. Ideally we would just use immortal so investigating this further.

Hi,

Would it be possible to integrate some kind of custom cleanup action after the process from “cmd” finishes? Something to be executed with the exit code as a parameter, that could perform some extra actions before the main process is restarted (or just after it is shut down.)

I have a 'cmd' script that uses “exec” to start the main service so that it can be managed properly, but when it stops I'm left with a few ifconfig commands to run to ensure the proper teardown sequence 😅

When downloading the precompiled binaries, this error may appear:

 Error looking up user: "www". user: Lookup requires cgo

Seems that is not currently possible to cross compile using cgo, therefore need to way to create the binaries on the native platforms.

Compiling from sources solves this problem.

https://golang.org/cmd/cgo/

We use immortal to configure some code insider our docker containers. Depending on some external configuration, we may want our service to always be restarted, or to run just once.

I tried setting retries to 0 in immortal configuration but that didn't seem to do it.

Any way i can use immortal so that supervisor exits if service exits, using run.yml approach?

Improve the overall documentation, for the example in the run.yml there is no explanation about how to avoid rotating logs, something that could be done by just omitting the options age, num, size etc.

Be more clear, add more examples (avoid assumptions)

Relates to

• https://github.com/Homebrew/homebrew-core/pull/45928
• https://github.com/Homebrew/homebrew-core/pull/47622

It looks like we cannot build immortal from the source code (I just tried on my local machine, I wonder if you can provide some instructions to keep the formula up to date). Thanks!

cc @nbari

This adds a -n flag to immortal which does not make it fork to the background. This is useful for testing and also in cases immortal is executed from another processes which wants it to stay in the foreground.

immortaldir does not start services when running immortal entirely from a user $HOME -- with no access to root directories.

Setup

$HOME/local/bin/immortal
$HOME/local/bin/immortaldir
$HOME/local/bin/immortalctl
$HOME/local/var/run/immortal
$HOME/local/etc/immortal/app.yml

Success with immortal

cd $HOME/local
./bin/immortal -c etc/immortal/app.yml

This works; bin/immortalctl status shows the service started & app is running. I can stop, restart, and otherwise control app through immortalctl as expected. However...

Failure with immortaldir

cd $HOME/local
IMMORTAL_SDIR=$HOME/local/var/run/immortal ./bin/immortaldir etc/immortal

results in

2018/04/17 22:28:36 immortal scandir: /home/uzr/local/etc/immortal
2018/04/17 22:28:36 Starting: app
2018/04/17 22:28:36
2018/04/17 22:28:41 Starting: app
2018/04/17 22:28:41

and so on, repeatedly. No errors, no logging, no way to figure out what's going wrong. app is not started nor is running.

Expected behavior

An app that can be successfully started with immortal should work when started with immortaldir.

• [x] Have you test the code?
• [x] Have you check that the existing tests are passing?
• [x] The destination branch is develop?

@nbari you need to generate a PAT and encrypt the setting so that we can automate this flow.

Ref: https://github.com/mislav/bump-homebrew-formula-action

Ref #12

How do I ensure the network is configured by dhcp prior to running my command? The equivalent of systemd's After=network.target or After=network-online.target

Bumps nix from 0.15.0 to 0.20.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

improve tests for scandir.go and watchdir.go mainly the onew using kqueue (freebsd netbsd openbsd dragonfly darwin)

func (s *ScanDir) Start(ctl Control) {}

and

func (s *ScanDir) Scandir(ctl Control) error {}