Comments for 5p.dk http://www.5p.dk Random thoughts and programming Wed, 25 Jan 2012 19:59:12 +0000 hourly 1 http://wordpress.org/?v=3.0 Comment on Requests by Tobias http://www.5p.dk/tinyshell/requests/comment-page-1/#comment-681 Tobias Wed, 25 Jan 2012 19:59:12 +0000 http://www.5p.dk/#comment-681 I uses TinyShell on a Server with debian Squeeze and Apache browsing with Firefox 9.0 and become this Error: <code>Notice: Undefined index: tssid in /var/www/tinyshell/header.php on line 26</code> I uses TinyShell on a Server with debian Squeeze and Apache browsing with Firefox 9.0 and become this Error:

Notice: Undefined index: tssid in /var/www/tinyshell/header.php on line 26
]]> Comment on TinyShell by Theis Mackeprang http://www.5p.dk/tinyshell/comment-page-1/#comment-378 Theis Mackeprang Mon, 24 Oct 2011 08:39:09 +0000 http://www.5p.dk/#comment-378 Sorry, I cannot remember what program I used. But it was freeware. Sorry, I cannot remember what program I used. But it was freeware.

]]> Comment on TinyShell by Insane User http://www.5p.dk/tinyshell/comment-page-1/#comment-369 Insane User Mon, 17 Oct 2011 23:05:45 +0000 http://www.5p.dk/#comment-369 Off topic question, what did you use to record the screen to create the demo above? It was used in, "http://www.youtube.com/v/BvPcwhqcmTk?fs=1&hl=da_DK&rel=0" Off topic question, what did you use to record the screen to create the demo above?

It was used in, “http://www.youtube.com/v/BvPcwhqcmTk?fs=1&hl=da_DK&rel=0″

]]> Comment on FAQ by TinyShell, ssh like access to your website | Wildeng TechDad http://www.5p.dk/tinyshell/faq/comment-page-1/#comment-368 TinyShell, ssh like access to your website | Wildeng TechDad Mon, 17 Oct 2011 20:38:36 +0000 http://www.5p.dk/#comment-368 [...] Download it from here [...] [...] Download it from here [...]

]]> Comment on Localhost Slow on Windows 7 by JC http://www.5p.dk/localhost-slow-on-windows-7/comment-page-1/#comment-193 JC Sat, 12 Mar 2011 19:20:58 +0000 http://www.5p.dk/?p=534#comment-193 This is because it's trying IPv6 before IPv4. Disabling the IPv6 stack or just configuring your browser to not use IPv6 also works for this problem. This is because it’s trying IPv6 before IPv4. Disabling the IPv6 stack or just configuring your browser to not use IPv6 also works for this problem.

]]> Comment on FAQ by Theis Mackeprang http://www.5p.dk/tinyshell/faq/comment-page-1/#comment-190 Theis Mackeprang Wed, 23 Feb 2011 13:00:01 +0000 http://www.5p.dk/#comment-190 Regarding SSH, you might want to copy the sys plugin to an ssh plugin and have a look at this: http://www.php.net/manual/en/function.ssh2-exec.php Unfortunately I do not have think most users have a need to create an SSH connection from the web server to another server through TinyShell, or even have enabled the requirements in PHP to do so, so I have not considered making such a plugin. And again, if you feel like doing some development on TinyShell, please tell me ;-) Regarding SSH, you might want to copy the sys plugin to an ssh plugin and have a look at this: http://www.php.net/manual/en/function.ssh2-exec.php Unfortunately I do not have think most users have a need to create an SSH connection from the web server to another server through TinyShell, or even have enabled the requirements in PHP to do so, so I have not considered making such a plugin. And again, if you feel like doing some development on TinyShell, please tell me ;-)

]]> Comment on FAQ by Theis Mackeprang http://www.5p.dk/tinyshell/faq/comment-page-1/#comment-189 Theis Mackeprang Wed, 23 Feb 2011 12:43:13 +0000 http://www.5p.dk/#comment-189 I never realized that PHP would actually wait forever for the command to execute and then also cause the web server to hang. I made a few tests, and it seems that system calls are not affected by the PHP max_execution_time/set_time_limit functions. Actually I also thought that web servers like Apache was configured by default to kill the PHP process after an amount of time, but I see that this is not always the case. But for now I suggest that you open sys.php in the plugin folder and either: 1. Create a black-list of unsupported commands you type by mistake. 2. Alter the shell_exec command, such that output is piped into a file and force a new process by adding an ampersand (&) in the end all commands (where it now already redirects the error stream to standard out). Then cat or tail this file for output after each system call. Problem is that you need to kill all the open process at some time if the do not terminate, but you will probably figure out a way to do this, or maybe do it when you have physical access to the server. 3. Modify the sys plugin to use proc_open instead of shell_exec, in order to gain control over the process that is started. I think I will look at implementing the last solution in the near feature, and if you do, please share. Thanks for bringing up the problem :-) I never realized that PHP would actually wait forever for the command to execute and then also cause the web server to hang. I made a few tests, and it seems that system calls are not affected by the PHP max_execution_time/set_time_limit functions. Actually I also thought that web servers like Apache was configured by default to kill the PHP process after an amount of time, but I see that this is not always the case. But for now I suggest that you open sys.php in the plugin folder and either:

1. Create a black-list of unsupported commands you type by mistake.
2. Alter the shell_exec command, such that output is piped into a file and force a new process by adding an ampersand (&) in the end all commands (where it now already redirects the error stream to standard out). Then cat or tail this file for output after each system call. Problem is that you need to kill all the open process at some time if the do not terminate, but you will probably figure out a way to do this, or maybe do it when you have physical access to the server.
3. Modify the sys plugin to use proc_open instead of shell_exec, in order to gain control over the process that is started.

I think I will look at implementing the last solution in the near feature, and if you do, please share. Thanks for bringing up the problem :-)

]]> Comment on FAQ by Peter Valdemar Mørch http://www.5p.dk/tinyshell/faq/comment-page-1/#comment-188 Peter Valdemar Mørch Mon, 21 Feb 2011 21:47:14 +0000 http://www.5p.dk/#comment-188 Hi, I understand and accept that I can't use vi or top or whatever. That they won't work. But TinyShell should survive if I by mistake try to use them anyway. I should be able to get my prompt back somehow. The problem is that I if I by mistake type "vi file" I'm toast. I cannot CTRL-C, or reload the browser or anything. I need to restart the web server (by some other means) to get anything working again. That means I cannot rely on it. If TinyShell access is all I have, "vi file" means I loose connection to the server forever. A <a href="http://www.google.com/search?q=truck%20roll" rel="nofollow">truck roll</a> is required. Here in my debug environment I do have normal terminal access. But once we've gone live, I won't have that. Only HTTP access to serverA. For some reason that I don't understand it isn't possible from a TinyShell on serverA to ssh to serverB. Once live I won't have terminal access to any of them - only TinyShell access. And its a shame I won't be able to get anywhere from serverA via SSH, don't you think? I hope I've been more clear this time! :-) Hi, I understand and accept that I can’t use vi or top or whatever. That they won’t work. But TinyShell should survive if I by mistake try to use them anyway. I should be able to get my prompt back somehow. The problem is that I if I by mistake type “vi file” I’m toast. I cannot CTRL-C, or reload the browser or anything. I need to restart the web server (by some other means) to get anything working again. That means I cannot rely on it. If TinyShell access is all I have, “vi file” means I loose connection to the server forever. A truck roll is required.

Here in my debug environment I do have normal terminal access. But once we’ve gone live, I won’t have that. Only HTTP access to serverA. For some reason that I don’t understand it isn’t possible from a TinyShell on serverA to ssh to serverB. Once live I won’t have terminal access to any of them – only TinyShell access. And its a shame I won’t be able to get anywhere from serverA via SSH, don’t you think?

I hope I’ve been more clear this time! :-)

]]> Comment on FAQ by Theis Mackeprang http://www.5p.dk/tinyshell/faq/comment-page-1/#comment-186 Theis Mackeprang Mon, 14 Feb 2011 17:02:09 +0000 http://www.5p.dk/#comment-186 Hi, you are right ;-) TinyShell is not a real terminal, it does not support (n)curses programs, like top, vi, vim, etc. But you can use the plugin called tiny to edit files. Regarding SSH and top, unfortunately you will have to make a new plugin to support this. But if you have access to do this already, why don't you use SSH directly instead of TinyShell? TinyShell is more ment to upload to FTP servers, where one does not have shell access. You should be able to call $apache restart though, but it requires that PHP has the right access to perform the command. Hi, you are right ;-) TinyShell is not a real terminal, it does not support (n)curses programs, like top, vi, vim, etc. But you can use the plugin called tiny to edit files. Regarding SSH and top, unfortunately you will have to make a new plugin to support this. But if you have access to do this already, why don’t you use SSH directly instead of TinyShell? TinyShell is more ment to upload to FTP servers, where one does not have shell access. You should be able to call $apache restart though, but it requires that PHP has the right access to perform the command.

]]> Comment on FAQ by Peter Valdemar Mørch http://www.5p.dk/tinyshell/faq/comment-page-1/#comment-185 Peter Valdemar Mørch Mon, 14 Feb 2011 10:43:41 +0000 http://www.5p.dk/#comment-185 Hejsa, I've just given TinyShell a quick spin. Great! I'm having trouble with vi/vim and ssh though; two important tools... I have discovered that it doesn't give me a real terminal: <code> $ top TERM environment variable not set. </code> Fair enough. Worse, though, is that if I try to launch vim (from vim-gtk), the prompt just disappears and I can't seem to get it back. Refreshing the browser page also doesn't work. I have to restart apache. Which is only possible if I have a command line to the server. A chicken-and-egg situation. I also would like to be able to use ssh to get from that server to another. But: <code> $ ssh -l pvm otherserver Host key verification failed. </code> I'm not sure why that is. If I try this from a real terminal, it works fine. <code> > sudo -H -u www-data sh server@www-data:~/path> ssh -l pvm otherserver The authenticity of host 'otherserver (172.22.216.60)' can't be established. RSA key fingerprint is (hidden). Are you sure you want to continue connecting (yes/no)? </code> Hejsa,

I’ve just given TinyShell a quick spin. Great!

I’m having trouble with vi/vim and ssh though; two important tools…

I have discovered that it doesn’t give me a real terminal:

$ top
TERM environment variable not set.

Fair enough. Worse, though, is that if I try to launch vim (from vim-gtk), the prompt just disappears and I can’t seem to get it back. Refreshing the browser page also doesn’t work. I have to restart apache. Which is only possible if I have a command line to the server. A chicken-and-egg situation.

I also would like to be able to use ssh to get from that server to another. But:

$ ssh -l pvm otherserver
Host key verification failed.

I’m not sure why that is. If I try this from a real terminal, it works fine.

&gt; sudo -H -u www-data sh
server@www-data:~/path&gt; ssh -l pvm otherserver
The authenticity of host 'otherserver (172.22.216.60)' can't be established.
RSA key fingerprint is (hidden).
Are you sure you want to continue connecting (yes/no)?
]]>