[GH-ISSUE #41] SSH + daemonize not working #25

Closed
opened 2026-03-03 16:03:48 +03:00 by kerem · 3 comments
Owner

Originally created by @mdelapenya on GitHub (Feb 20, 2015).
Original GitHub issue: https://github.com/mthenw/frontail/issues/41

Hi, first of all, thanks for this really cool tool! It is exactly what I need to share some server logs.

For that, I tried the SSH configuration with daemonize enabled, but it does not work for me, it's always using the false branch on tail.js (local execution).

This is the command I execute:

frontail --remote-host REMOTE_IP --remote-user REMOTE_USER -p 7777 -n 50  --ui-highlight default.json -d --log-path /tmp/frontail.log REMOTE_PATH_TO_MY_LOG

Adding this trace:

console.log("SSH OPTIONS: " + program.remoteHost + " - " + program.remoteUser + " - " + program.remotePort);

it returns "SSH OPTIONS: null - root - 22", although I passed the variables

On the other hand, removing the daemonize commands, it works as expected.

I believe that the sshOptions variable is not set when daemonizing the program. I'd try to fix it by myself, but I'm not a node expert :S

Thanks!

Originally created by @mdelapenya on GitHub (Feb 20, 2015). Original GitHub issue: https://github.com/mthenw/frontail/issues/41 Hi, first of all, thanks for this really cool tool! It is exactly what I need to share some server logs. For that, I tried the SSH configuration with daemonize enabled, but it does not work for me, it's always using the false branch on tail.js (local execution). This is the command I execute: ``` shell frontail --remote-host REMOTE_IP --remote-user REMOTE_USER -p 7777 -n 50 --ui-highlight default.json -d --log-path /tmp/frontail.log REMOTE_PATH_TO_MY_LOG ``` Adding this trace: ``` console.log("SSH OPTIONS: " + program.remoteHost + " - " + program.remoteUser + " - " + program.remotePort); ``` it returns "SSH OPTIONS: null - root - 22", although I passed the variables On the other hand, removing the daemonize commands, it works as expected. I believe that the sshOptions variable is not set when daemonizing the program. I'd try to fix it by myself, but I'm not a node expert :S Thanks!
kerem closed this issue 2026-03-03 16:03:48 +03:00
Author
Owner

@mthenw commented on GitHub (Feb 23, 2015):

Hi @mdelapenya,
I was on vacation during previous week. I will look at it later today.

<!-- gh-comment-id:75555018 --> @mthenw commented on GitHub (Feb 23, 2015): Hi @mdelapenya, I was on vacation during previous week. I will look at it later today.
Author
Owner

@mdelapenya commented on GitHub (Feb 23, 2015):

Thanks @mthenw! I sent you a pull with test too #42

<!-- gh-comment-id:75555768 --> @mdelapenya commented on GitHub (Feb 23, 2015): Thanks @mthenw! I sent you a pull with test too #42
Author
Owner

@mthenw commented on GitHub (Feb 23, 2015):

@mdelapenya published v.1.4.1 (b85c828)

<!-- gh-comment-id:75624936 --> @mthenw commented on GitHub (Feb 23, 2015): @mdelapenya published v.1.4.1 (b85c828)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/frontail#25
No description provided.