![]() |
![]() ![]() shell |
Subcategories:
Answers in this category: | |
![]() |
![]() ![]() ![]() shell does not work |
shell access is not enabled by default, therefore telnet and ssh do not work without an extra hardcopy application. More to read at shell policy http://www.polarhome.com/service/policy.html faq | |
![]() |
![]() ![]() ![]() how to use ssh with portforward? |
telnet and ssh work nice with portforward, but you have to telnet to some defined port descried at http://www.polarhome.com/service/shell/ports.html
Example: | |
![]() |
![]() ![]() ![]() did I lost my shell account? |
If your username is on the list http://www.polarhome.com/hacker/users.deny you did.
Please use http://www.polarhome.com/service/network/net-finger.html - finger service to query your host for your username in order to get exact information about your account status.
- if account does not exist - your account has not been created ot it is deleted | |
![]() |
![]() ![]() ![]() can I run eggdrop, BNC and ircd from shell |
Yes, you can. You can upload, compile, build, run bg processes and use all available programs and resources on the system. Shell is as open as it was earlier (now even with crontab). eggdrop, BNC and other irc servers, bouncers, proxies and non destructive bots are not considered to be malicious.
faq | |
![]() |
![]() ![]() ![]() I had a shell account at polarhome.com. What should I do |
Your earlier account have been transformed to ftp account. Existing accounts have not been deleted and all content have been kept. Otherwise, you may choose among the following alternatives:
- continue to use as ftp user | |
![]() |
![]() ![]() ![]() how many BG-s may I run |
polarhome does not have BG limit just total process limit, but if you start too many BG processes you will not be able to manage your account any more.
faq | |
![]() |
![]() ![]() ![]() crontab problems? |
Shell accounts do have enabled crontab. Crontab may hava a strange behaviour that you may submit a new one but you can not edit it any more with crontab -e. The problem lays in VIM editor secure temporary file handling. There are two solutions: 1. use another editor for crontab. $ export EDITOR=pico $ crontab -e
2. delete curent crontab and submit a new one |
Next: |
![]() |
|
Vote for polarhome |