idle daemon message

[Rosli Ahmad]

Hi,
I'm having this message:
This user id is logged on too many times. Please end
some logins to reduce your total number of logins to no
more than 1. Please do so in the next 2 minutes
or you will be logged out by the system.

I believe this is managed thru the idle.cf file, but wondering how do I go about in handling the situation above. Pls. advise.

Thank you.
-rosli-

[Michael Tully]

You obviously have some customised script running that looks to see how mnay time a user is logged in. By default the system does not do this.

Have a look in either cron for the approprate script that runs, or it could be running from within /etc/profile. If you are not sure you could do a comparison between /etc/profile and a system backup file in /usr/newconfig/etc/profile

You could also post the contents of idle.cf if you wish.

[U.SivaKumar_2]

Hi,

you have not elaborated on the system and setup you are using. are you using PAM or RADUIS based login ?

Try increasing maxuprc kernel paramter and rebuild the kernel.

regards,

U.SivaKumar

[Rosli Ahmad]

Hi,
I was under the impression that the control is a standard feature if HP-UX, instead of cron'ed job. Does this mean that by default there's no facility in monitoring concurrent login without have trusted system? Anyway, the idle.cf is attached and I'll look for the specific cron then.

As for the system, it's a K-class server,
runing HP-UX 11.00.

thanks
-rosli-

[Michael Tully · Accepted solution]

That is a customised config file for sure that uses a cusomised script. I've never seen HP supply any script where there have been notations referring to users as dopey and stupid. There is a master script that makes reference to this file. Is there one running from /etc/profile? If not it must be from cron, perhaps wth a sleep in it, or from /sbin/init.d that runs in the background.

[Steven E. Protter]

That is not a standard HP-UX feature. Its an open source add in available for many forms of Unix.

You need to figure out who this is running and stop it if its causing you problems. We considered and rejected installation of such scripts back in 1995. They ran out of cron.

You can write your own, less obnoxious script pretty easily.

SEP

[Rosli Ahmad]

Well, I guess so. We'd probably need to relook at reason why it was there in the first place, my bet is to control concurrent login.
Any thread or scripts that would do the same job, but in a rather less complex manner?
thank you.

regards
-rosli-