config.conf error line 1 [solved]

[Cr4sh]

A stupid question:"Which is the correct syntax to define the eggdrop path?"

[nml375]

If you're referring to the line saying something like this:

Code: Select all

#! /path/to/eggdrop

Then it's the "magic number" for scripts (aka "shebang"), which tells the shell (bash, etc) which binary to start this script with. Thus, this is only needed if you'd like to be able to start your eggdrop with a command such as this:

Code: Select all

# ./eggdrop.conf

It's not needed to start your eggdrop the "normal" way:

Code: Select all

# ./eggdrop eggdrop.conf

The proper value though?
Lets say we've installed your eggdrop binary in the folder "eggie" under our home ("/home/me"); then this would be set to:

Code: Select all

#! /home/me/eggie/eggdrop

Keep in mind, that many shells have a limit of 32 characters including the #! prefix, so if you've got a long path to the installation, this might not even be an option for you..

Oh, and no, this will not work with windrops..

[Cr4sh]

In any case i received

Code: Select all

$ ./eggdrop -m config.conf

Eggdrop v1.6.19 (C) 1997 Robey Pointer (C) 2008 Eggheads
[20:27] --- Loading eggdrop v1.6.19 (Sat Dec 11 2010)
[20:27] Tcl error in file 'config.conf':
[20:27] invalid command name "#!"
    while executing
"#! /home/cr4sh/eggdrop"
    (file "config.conf" line 1)
[20:27] * CONFIG FILE NOT LOADED (NOT FOUND, OR ERROR)

[nml375]

That is odd, anything starting with a hash (#) should be treated as a comment in tcl. Try completely removing that line

[Cr4sh]

a new error message

Code: Select all

$ ./eggdrop config.conf

Eggdrop v1.6.19 (C) 1997 Robey Pointer (C) 2008 Eggheads
[20:37] --- Loading eggdrop v1.6.19 (Sat Dec 11 2010)
[20:37] Tcl error in file 'config.conf':
[20:37] invalid command name "#"
    while executing
"# ^- This should contain a fully qualified path to your Eggdrop executable."
    (file "config.conf" line 1)
[20:37] * CONFIG FILE NOT LOADED (NOT FOUND, OR ERROR)

[nml375]

Then it would seem you've got a bad tcl interpreter. Did you use the gentoo package for installing tcl?

[Cr4sh]

Yes, i've emerge tcl directly from portage package.

[nml375]

That... is very odd.
I suppose you could try and manually build and install tcl from www.tcl.tk, and then rebuild your eggdrop against this..

Also, you could try starting "tclsh" (a tcl shell interpreter), and try to run a simple script within it such as below:

Code: Select all

puts stdout "Starting up... next comes a comment..."
# This is the first comment..
#This is the second one...
puts stdout "If you see this, just below the \"Starting up\" line, comments seem to work as intended"

put it in a text file, and start it like this:
tclsh yourscript.tcl

[Cr4sh]

And the result is

Code: Select all

H4ckmaniac Desktop # tclsh try.tcl
Starting up... next comes a comment...
If you see this, just below the "Starting up" line, comments seem to work as intended

[nml375]

Unfortunately, I'm running very low on ideas.. eggdrop simply passes the filename of the config-file to "Tcl_EvalFile", just like loading it with tclsh..

[Cr4sh]

Thanks man, it's not a problem, in any way i will resolve this question.

Portage, has just a packet "net-irc/eggdrop" to the 3.6.19 that works perfectly