egghelp.org community

[DJCharlie]

Afternoon all. I'm having a bit of trouble with a small script, and can't find the error I'm getting ANYWHERE else.

The error is:

[nml375]

Try and get the value of ::errorInfo right after triggering the error. You might have to enable the .set or .tcl dcc partyline command (see your configfile for details on this), then type either ".set ::errorInfo" or ".tcl set ::errorInfo" after triggering the error.

My suspicion right now though, is that it's caused by the centerim command in your bash-script, possibly from being executed from your eggdrop directory. Just a guess right now though..
_________________
NML_375, idling at #eggdrop@IrcNET

[DJCharlie]

[nml375]

Just downloaded and compiled centerim myself. After attempting a similar message (though over icq), I managed to generate the exact same error message. That strengthens my suspisions of centerim. I also get the very same result if I launch it through a bash-shell.

I find it odd that ::errorInfo would be 0, as it should atleast hold the actual error message (+ extra information leading up to the error).

Unfortunately, I'm out of other ideas, the putserv tcl-command will not generate that error under any condition, and as you said you've tried ruling out each line of your bash-script, I frankly don't know where to look further other than re-checking everything over and over..
_________________
NML_375, idling at #eggdrop@IrcNET

[DJCharlie]

[nml375]

There are two differences when a bash-script is started from the command line and using exec within eggdrop;

• The environment;
  The bash-script will inherit the environment of the parent process, containing such settings as PATH, and similar. This becomes very prominent if you started your eggdrop through a cronjob - as this usually only provides the very most rudimentary environment. Try this from the partyline:
  

  Code:

  .tcl array get ::env

  
  This should retrieve the full set of environment variables as seen by your eggdrop. Then compare that from using the "set" command from your bash-shell...
  
  
• Current Working Directory;
  This too is inherited from the parent process. Eggdrop's are usually started from within the directory where it was installed, while you most commonly use your shell directly from the home directory. If centerim cannot differentiate between these, I could very well see it throwing errors such as the earlier mentioned ones..

_________________
NML_375, idling at #eggdrop@IrcNET