Topic: e-smith-dialin

[Lloyd keen]

I've been trying to setup dial-in on the e-smith server and I used the e-smith-dialin-.2.5 rpm I think from memory because I'm running 4.1.1 but after installing this and mgetty I'm unable to access the e-smith-manager. Should I revert back to 2.4 or is there a fix that I can apply to fix the access problem with e-smith-dialin 2.5?

[Stephan Burmeister]

Just re-install the e-smith-base RPM with the --force option and you can access the e-smith-manager again.

[Charlie Brady]

Stephan Burmeister wrote:
 
> Just re-install the e-smith-base RPM with the --force option
> and you can access the e-smith-manager again.

That is unlikely to fix the problem. However, removing the e-smith-dialin RPM, and doing:

/sbin/e-smith/signal-event console-save

should fix the problem.

The problem is likely to be the e-smith-dialin RPM not being compatible with e-smith 4.1.x.

Regards

Charlie

[Stephan Burmeister]

Well, it did work for me...
I had the exact same problem on two different linux boxes. After re-installing the e-smith-base RPM I could access the e-smith-manager again and also dial in to those boxes.

[Steve Hobbs]

Hi guys.  Stephan is correct. Charlie, I removed the e-smith-dialin (after installing is when my web acess to the e-smith manager was cut off) and ran the command you suggested.  That did not "fix" the problem.

I am new to e-smith, but have some experience with Apache and Linux.  It looks like the e-smith-dialin rpm is not quite ready for 4.1.1 It is over writing one of the template scripts incorrectly and re-installing the base rpm seems to restore them

Steve