On Tue, Dec 05, 2000 at 10:49:23PM -0500, Eireann Lewy wrote:
> Okay. An update:
>
> 1) the /etc/profile is in fact profile and not .profile. This is what
> happens when one e-mails when running on a negative amount of sleep and
> such.
>
> As for recreating that whole making-a-dir-with-bad-perms thing I don't
> think I can do it because whenever I mkdir it has correct perms,
> regardless of how I am logged in (i.e. my normal user vs. root vs.
> anything else). Perhaps that was just a fluke. In any case, my people
> have been alerted as to how to chmod and chown now and know when and
> when not to play with those ever-so-powerful commands. ;)
>
> The "I can't FTP" thing...well that was just very sad. Despite my
> co-admin being warned that I need actual information when she's
> reporting a problem, ("Saying, "I can't FTP" is like saying "I don't
> really feel good," to a doctor) she didn't explain to me that "I can't
> FTP" really means she can log in and can play around in any directory
> but the one with the bad perms. ;)
>
> Maybe that whole thing with making the directory was a fluke. Like I
> said, when I make new dirs, I get 755 perms. She got 644 on her newly
> made directory, which is bad, considering it renders CD useless. ;)
>
> As for the CGI, it still does not work. I entered the line earnest told
> me to enter. I did so using "echo" (which is what the rest of the file
> uses) as well as using print. I tried with and without a semi-colon on
> the end. I restarted httpd after each change. No help. So now I am
> pasting the file. This is for a script which runs finger on the machine
> and prints the e-mail addie to the web user.
>
> There is one other script which is not working, but since someone else
> coded it and he has 13+ scripts in his directory all named things which
> lead me to believe it could be ANY of them and I don't understand CGI I
> am just pasting this one and going to assume that the both need the same
> change and/or ask him what the hell file it is... *sigh*
>
> Yeah. I reiterate my suckiness. Here is the script (please excuse
> naughty language: geeks which are not me having fun, apparantly...:
>
> #!/usr/bin/csh -f
>
> set fuck=`echo $QUERY_STRING |sed s/yum=/\ /g`
>
> echo "Content-type: text/html\n\n"
> echo ""
What's the use of \n _and_ an empty echo, the just do the same, not?
are the \n's recognized by echo? They aren't in bash at least, the
/bin/echo does not, and bash' echo neither.
> echo "<HTML>"
> echo "<body bgcolor=white text=black link=red>"
> set fucko=`echo $fuck|grep +`
>
> if( $fucko == $fuck ) then
> echo "Please enter only one name, first or last, at a time."
> else
> finger [EMAIL PROTECTED]>./result
>
> set fucke = `cat ./result |grep finger:`
> echo $fucke
> echo `cat ./result |./login`
> endif
> echo "</body>"
>
> echo "</html>"
>
> Again, Apache says it's a matter of premature headers (I think. Been a
> few days), and the web browser translates that into: There has been an
> internal error, please e-mail webmaster@<Erin'sdomain>.edu
--
,-------------------------------------------.
> Name: Alson van der Meulen <
> Personal: [EMAIL PROTECTED] <
> School: [EMAIL PROTECTED] <
`-------------------------------------------'
The drive ate the tape but that's OK, I brought my screwdriver.
---------------------------------------------
