Sonic.net

slapout wrote:How do I run the ancient calendar program, "pal"?
a dozen years ago I learned some unix for the purpose off running pal twice a day in cron, with two sets of parameters.
In oldshell I traced it to

slapout~: whereis pal
pal: /usr/bin/pal /etc/pal.conf /usr/share/pal /usr/share/man/man1/pal.1.gz

It still executes in oldshell. How do I get it to execute in sh? (sh.sonic.net)

I hadn't installed it. (It isn't part of the CentOS repositories.)

I found the sources that were used to install it on Bolt, and it is now installed on sh.

-Scott

scott wrote:

• Currently, there isn't an auto-logout set by default. (You can set your own with tcsh or bash, though.)

Do we want there to be an auto-logout, and if so, what do folks think the timeout value should be?

There is an auto-logout, and it's driving me nuts. oldshell doesn't have one, but not even a vim or tail session on sh disables its auto-logout. (Either one suffices on Linux hosts at work.)

I don't care if sh defaults to auto-logout as long as I have a way to defeat it. I really, really do not want to have to re-login multiple times per day, or even per month. :-(

Thanks,
Greg

warriorz wrote:Thanks Scott,

One last clarification. I want to forward mail to the IMAP folders. What path do they appear under ?

Hi, sorry for my late reply -- had to make sure I knew how to do this properly first.

Basically, you set things up like this:
This will put mail with "proctest" in the header in the IMAP folder "PROCTEST". If the folder's spool directory doesn't exist, it will be created.

Note that you still need to subscribe to the folder with your IMAP client.

To find out the value for "MAILDIR", use the command "wheresthemail.pl" on either shell server, and remove the trailing slash from the path name.

I can see that this should be added to the wiki, and we'll do that.

Hope that helps.

-Scott

roelofs wrote:scott wrote:

• Currently, there isn't an auto-logout set by default. (You can set your own with tcsh or bash, though.)

Do we want there to be an auto-logout, and if so, what do folks think the timeout value should be?

There is an auto-logout, and it's driving me nuts. oldshell doesn't have one, but not even a vim or tail session on sh disables its auto-logout. (Either one suffices on Linux hosts at work.)

I don't care if sh defaults to auto-logout as long as I have a way to defeat it. I really, really do not want to have to re-login multiple times per day, or even per month.

Thanks,
Greg

Hi Greg,

I can't think of a reason why sh is hanging up on you. I will see if I can't track that down. It might have something to do with tcsh, since my bash sessions don't time out...

-Scott

Hi Scott,

Can we get ncurses installed please? Had it on the old shell, and I use(d?) it fairly often

Dan

I got this email from an unknown email appearing as Sonic. Since I DO NOT click on links in emails from those I do not know, ([email protected] – an email address which has never emailed me before,) it was suspect.

I am not sure who on Sonic's staff wrote this email, but you might want to tell whatever techie wrote this email for you that:
1. they should reduce their techno-speak of terms non-techies do not know (e.g. crons, shell extensions, etc.) into understandable English!
2. think in the mind of a customer getting this - especially a non-techie:
Do I need to do something? Does this affect my email extension or anything to do with my hosted site?

Whoever wrote the email should also be instructed on anticipating questions like this which customers might have! I would also recommend that techie emails should be run by non-techie people prior to being sent out so that the tech terminology can be explained in English. (As a seasoned marketer of many years, this email is indicative of many techies. It is also indicative of being written by someone who does not think in advance of what customers might want to know, be concerned about, etc. I have written emails for many techies at many companies and can tell you that if a communications piece cannot be understood by a 10-year old, and has not thought out questions in the eyes of a customer beforehand, they will fail, as this one has.)

Then I called Sonic tech support and basically got a version of what other companies call tech “support” – (which I have not known Sonic for - until now.) This version of “support” assumes that people want to have their time wasted by digging through forums and wikis. I do not. This is the reason I have gone with and stayed with Sonic for my hosting for years. PLEASE do not sink to the pathetic level of support where one is pawned off to flail on the Internet e.g. forums, wikie's, etc.) to find answers to questions which should have been in an email of this type. This is not what I have come to know and love Sonic for.

I run one company and am launching a startup and as a non-techie the last thing I need is to learn what a shell and a cron are, if this affects me, and how, and how I get support which does not waste my time on forums and wikis I do not understand as a non-techie.

Please advise as a computer hassle is the last thing I need right now. Hearing from a human being offline or by email would be preferable to a tech forum as I do not go to nor wish to.

A very satisfied customer, until now,
Leslie Sheridan

I am finally catching up to the new shell server, but I cannot log in.

I used Tera Term SSH and Putty under SSH. When I used Tera Term it says username and passphrase - and I type in the same username and password as I did with bolt. It doesn't work. With Putty it asks for a login, secret token, and password. I use the password for both the secret token and password, and it doesn't work.

However, I then use Tera Term to ssh to bolt again. From bolt, I type % ssh [email protected] and when I type in my password it works and I gain access to the sh.sonic.net server.

How can I access the sh.sonic.net directly with Tera Term or Putty?

Heya Scott, I'm still alive out here! Nothing at all is wrong, new shell server looking good to me. I checked to make sure my low water marks were still in place, QC pass.
Have a great day my friend, miss having y'all as an ISP...

Scott, I see that the topic of auto-logouts has come up again. I'd like the default to be at least an hour or two.

"qnmidas," if by "this email" you mean the one that was sent out today called "Shell server transition notification," do you not currently use the shell machine at Sonic? Last I heard, those announcements (the first one was, to the best of my knowledge, sent out in February) were only going to people who do use the shell, and thus would know the terminology referenced in the emails. If today's email went to the entire Sonic customer base, then yes, it should have said, "This message only applies to you if you use our shell server."

scott wrote:

scott wrote:

scott wrote:
That's a good point. I will make them accessible.

Okay, these now live in /logs/custweb, and I've created a symlink that will make the directory appear at /var/log/custweb .

Um, about that...

On further review, the custweb directory hasn't kept up with the times. Back in the day, it wasn't as big a deal to have real-time web logs for the entire web cluster available to everybody -- but that isn't in the cards for a modern environment.

So please use the /logs/by_user/ directory/directories to get the split-out web logs, and we'll see what we can do to get realtime logs to people _securely_.

Sorry if this is an inconvenience. Feedback appreciated.

-Scott

Hi,

I appreciate that my access logs are accessible under the new shell. Now I wonder if any progress has been made in giving us realtime access to the current log. Thanks.

Mike