in reply to Re^4: a classic : 'Premature end of script headers' problem
in thread a classic : 'Premature end of script headers' problem

If your answer to what I posted is '..trying to figure out what tail does..' Maybe you should not have root access on a server that serves outsite an intranet.

You should know to # man tail

You should really learn unix before you have that kind of control over a server.

If you know what you're doing, you can secure a machine like that to be a fortress. If you don't- and you have root.. you can blow yourself up- maybe even take some people with you.

I don't think there's any way I can prevent as coming accross as patronizing. I am sorry for that. I do not mean disrespect.

I am sure you can learn this up and down and left and right. But until you do- I must stress - don't open that thing to accept outside requests- via the internet.

A week or two of reading up could do a lot for you.

  • Comment on Re^5: a classic : 'Premature end of script headers' problem

Replies are listed 'Best First'.
Re^6: a classic : 'Premature end of script headers' problem
by hmbscully (Scribe) on Sep 19, 2007 at 19:08 UTC
    Before you panic, this is a development box that is pretty severely restricted by a firewall to only be open to internal users and I'm not running commands, beyond looking at files, as root personally. When I say I'm root, I mean it in the sense that I can be root or have my network admins do whatever I want. I'm not restricted by a hosting provider account.

    The last line was pretty patronizing. I've actually been working in unix for 7 years, but I've never had root access before the last 2 months, so I haven't yet learned a lot of the admin stuff. I'd love to have a couple weeks of free time to "read up."

    I learn more and more about less and less until eventually I know everything about nothing.
[reply]

In Section Seekers of Perl Wisdom