Yep, either you already got a process running, or it exited uncleanly leaving a "pidfile" behind...
Just do as the last line tells you to: Check if you already got a process running, otherwize remove the pidfile
Make sure you do not have a running process for the bot.hype wrote:how do you erase it?
Code: Select all
ps x
You will notice that I have highlighted the numbers on the left (in the above example) on the line containing information re eggdrop, that is the PID that needs to be killed if the eggdrop process is running.[chuckles@cristie ~/bots]$ ps x
PID TT STAT TIME COMMAND
73073 p0 SNs 0:00.02 -bash (bash)
95803 p0 SN 0:00.01 /home/chuckles/bots/eggdrop ./borg.conf (eggdrop-1.6.18)
96087 p0 RN+ 0:00.00 ps x
[chuckles@cristie ~/bots]$
Code: Select all
kill -9 <PID>
Code: Select all
rm pid.<botnick>
Then do the following and watch all of the output, it will show what is wrong:hype wrote:done that, well it seems that it doesen't go online
Code: Select all
./eggdrop -n eggdrop.conf