Problem with /etc/issue in RedHat Enterprise

[Skreemer]

We have a client dialing in to our RedHat box(it's set up as a BBS). Upon connection we present them a splash screen out of /etc/issue and or /etc/issue.net. When they log in after they see the splash screen they are issuing to us a carriage return. This places a CR when we are waiting for a username. They refuse to change the script so I have to come up with a work around. If I make it so we force a CR to move on to the login it will break other customers scripts.

Is there a way to pause for a tick or two at the issue screen to "ignore" the CR they send?

 

[macd68]

Needs to be reported to RH as a bug and fixed imo.

 

[mistoffeles]

Sounds to me like your customer is technically inept, and getting defensive about it. Perhaps you can offer to fix their broken script for them?

Alternately you can have some code that waits for an initial character, and if it's a CR it is thrown away, otherwise it proceeds normally. A timer delay really won't solve the problem, it will ignore it until such a time comes where it can jump up and bite you at the worst possible moment. I can foresee breaking other users' scripts with a timer easily enough as forcing a CR to be required. Really it's a problem with their script, not your host, if it is only with them and nobody else who uses your server. Standards exist for a reason, they make systems work togehter.