challenged with signal

[Junkone]

Hello
I am playing around with the jabber bot fron the link
http://nearlyfree.org/fun-jabber-bots.

I get a error at the following code next to trap. not sure why it is
happening. i thought you could send any string to trap a signal. can
someone help.

E:\Tools\CODE>ruby bot1.rb
bot1.rb:23:in `trap': unsupported signal SIGUSR1 (ArgumentError)
from bot1.rb:23



# Wait for the USR1 signal and read a message from ~/.jbot/message
trap("USR1") {
begin
bot.deliver(bot.master,File.new(File.join(home, "message")).read)
rescue Exception => e
puts e
end

 

[MonkeeSage]

Hello
I am playing around with the jabber bot fron the linkhttp://nearlyfree.org/fun-jabber-bots.

I get a error at the following code next to trap. not sure why it is
happening. i thought you could send any string to trap a signal. can
someone help.

The documentation for Kernel#trap wants to help...but you have to let
it.

E:\Tools\CODE>ruby bot1.rb
bot1.rb:23:in `trap': unsupported signal SIGUSR1 (ArgumentError)
from bot1.rb:23

# Wait for the USR1 signal and read a message from ~/.jbot/message
trap("USR1") {
begin
bot.deliver(bot.master,File.new(File.join(home, "message")).read)
rescue Exception => e
puts e
end

Regard,
Jordan

 

[Junkone]

The documentation for Kernel#trap wants to help...but you have to let
it.



Regard,
Jordan

Jordon. i understand u wnat me to read the docs which i did over and
over again before posting the question. i am still not getting the
answer to my prob. as per the ruby docs. << The first parameter is a
signal name (a string such as ``SIGALRM'', ``SIGUSR1'', and so on) or
a signal number. The characters ``SIG'' may be omitted from the signal
name>>
so what am i missing. appreciate help here.

seede

 

[Luis Lavena]

Hello
I am playing around with the jabber bot fron the linkhttp://nearlyfree.org/fun-jabber-bots.

I get a error at the following code next to trap. not sure why it is
happening. i thought you could send any string to trap a signal. can
someone help.

E:\Tools\CODE>ruby bot1.rb
bot1.rb:23:in `trap': unsupported signal SIGUSR1 (ArgumentError)
from bot1.rb:23

The error message wasn't too descriptive?

unsupported signal SIGUSR1, there you go.
USR1, USR2 and TERM are unsupported signal on Windows.

Only INT (INTERRUPT) is working.

HTH,

Luis

 

[Junkone]

The error message wasn't too descriptive?

unsupported signal SIGUSR1, there you go.
USR1, USR2 and TERM are unsupported signal on Windows.

Only INT (INTERRUPT) is working.

HTH,

Luis

thanks for letting me know. i guess i cannot trust the chm file too
much.
seede

 

[Gary Wright]

thanks for letting me know. i guess i cannot trust the chm file too
much.

The documentation for Kernel#trap doesn't mention that not
all signals are supported on all systems, but the documentation
for the Signal class is a bit better:

The list of available signal names and their interpretation is
system dependent. Signal delivery semantics may also vary between
systems; in particular signal delivery may not always be reliable.

It still doesn't give you a recipe for determining what signals
are available in your environment but at least it mentions that
this is system dependent.

Gary Wright