Login timed out after 60 seconds

[sihorton]

I am running a little proxy server using nodejs running on tinycore in a virtual machine. However once I had set everything up I noticed that tinycore automatically logged itself in on boot. I therefore added the bootoption:

noautologin

This is great as then at least you need to know the password to change settings in the machine. However it now displays the following:

Tiny Core
box login:
Login timed out after 60 seconds

Tiny Core
box login:
Login timed out after 60 seconds

and so on forever. Is there any reason to time out the login? Is there a way to just boot tiny core and run the services and then require a straight login before giving access to the machine -- i.e. can it just wait on the login prompt forever?

/Simon

[curaga]

Thanks for reporting. I have a patch for this, should be fixed in the next release.

[gerald_clark]

I actually like it the way it is.  I get a login prompt while onboot.sh is still starting services.
The timeout gives me a fresh unobscured  login prompt.

[curaga]

Hm, perhaps we should redirect bootlocal.sh's output to /dev/null then?

[gerald_clark]

I don't want it output to /dev/null.

[tinypoodle]

Casting my vote against that, I have always been relying on output of bootlocal, and also I think many issues of users would get obfuscated.

[Lee]

As bootlocal.sh is called from bootsync.sh and bootsync.sh runs after restore from mydata.tgz, can't each user have it according to his own preference?

[gerald_clark]

Yes he can, but the original post was about login timeout.

[sihorton]

Thanks curaga! Will be nice to skip the timeout messages, currently any errors on booting the machine scroll off the top of the screen to be replaced by these timeout messages so it will make things a lot nicer :-)

Looking forward to the next release.

/Simon

[aus9]

I hope the OP does not mind a slight hijack, or he might be interested?

As bootlocal.sh is called from bootsync.sh and bootsync.sh runs after restore from mydata.tgz, can't each user have it according to his own preference?

I do it this way
http://forum.tinycorelinux.net/index.php/topic,14310.msg80693.html#msg80693

what I have not said and what I should say is that I have a basic copy of vesa xorg.conf and a nvidia xorg.conf sitting in /opt ....opt is persistent and not in the .filetool.lst

b) The vesa bootlocal script installs the vesa xorg and the packages loaded come from vesa list
my vesa script has no sound and so no sound restored
c) The nv bootlocal script installs the nvidia xorg and the packages loaded come from nv.lst
my nv list has sound modules and so has sound levels restored
---the default alsa levels are not quite right for me....but I am an idiot

Note that I am lazy and used the bootcode "snd" when it does not have to do with sound, you can change that string to something else but I like short strings

Naturally my method does not have to involve xorg issues but I hope gerald_clark would like to share an easier way?

Yes he can

otherwise submitted to OP and Lee for their consideration

[Lee]

I do it this way
http://forum.tinycorelinux.net/index.php/topic,14310.msg80693.html#msg80693

Hmmm... so you specify a script to run as a boot code.  I like that.  I have to think about the whole thing for a while... moving over to the other thread for the thoughts, since this seems to be off of the original topic of this thread....

[sihorton]

Tested tinycore 4.7.5 with the noautologin boot parameter and it works as requested!

Thanks a lot for the fix.

/Simon