Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:1

BSD doesn't like su options in start-script?

posted by Krow on 09:00 AM April 9th, 2002   Printer-friendly   Email story
I'm using FreeBSD 4.5 Release, and for some odd reason my system does NOT like the part of the script that uses "su" for whatever reason, and i cannot figure it out. it doesn't like a particular "-" in it somewhere, but i cannot find it for the life of me. i'd really appreciate some help!
--
Dom LoBue
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • This is what I have on FreeBSD 4.3-RELEASE:

    if [ "$OS" = "FreeBSD" ] ; then
        su - $USERNAME -c "TZ=GMT $SLASHD SERVER_NAME" &
    elif [ "$OS" = "Linux" ] ; then
    [...]

    This is different from what is distributed (note the different arrangement of quotes.)
    • Yeah. I kept telling the slash guys (Cliff?) that the script didn't work. Needs double quotes not single. It looks EXACTLY like the Linux one.
      --

      --
      It's either on the beat or off the beat, it's that easy.
    • you rock.. that works perfectly!! but i'm also having a problem with apache.. it doesn't like lines 5 and 6 (i get an error on 6 when i comment out 5, haven't commented out both 5 and 6 yet tho) and apache won't come up if the include line for the slash conf is in there. here's the error: Syntax error on line 5 of /usr/local/slash/httpd/slash.conf: Invalid command 'AddHandler', perhaps mis-spelled or defined by a module not included in the server configuration and the lines 5 and 6 in slash.conf: AddHand
      --
      //- Dom LoBue
      aim(aa4544);icq(16681241);
      • haha! i just commented out those 2 lines, and then the next line becaue a synatx error. the whole entire slash.conf is a syntax error, LOL!
        --
        //- Dom LoBue
        aim(aa4544);icq(16681241);
        • Might one of those kinda programming errors like forgetting to close quotes. The parser then thinks the error is some lines after where the error actually is
          • i was thinking its because mod_perl wasn't installed, so installed the latest verion os mod_perl, and apache.

            now slash doesn't work at all..
            --
            //- Dom LoBue
            aim(aa4544);icq(16681241);
  • by Anonymous Coward
    That might help some.