seeing all login/logout [SOLVED]

[nordic bro]

What I want when booting is to see all services up to "local" starting; when I shutdown or restart I likewise want to see all services shutting down. I use verbose fbsplash, xfce ("exec ..." in ~/.xinitrc) and slim login mgr.

AFAIK these are my options:

1. use xdm to start slim
2. bypass xdm and start slim from /etc/conf.d/local.start in daemon mode
3. bypass xdm and start slim from /etc/conf.d/local.start NOT in daemon mode;

For #1, xdm starts slim WAY too early (after only about half the services have started); I also never see a single "xyz stopping" msg when rebooting/shutting down

For #2, when I shutdown or restart from xfce I get dropped back to slim's login screen then the machine reboots/shuts down from there - not a single msg about "xyz stopping"

For #1 and #2 I think they're related to udev104 since I never had this undesirable behavior before emerge'ing it (and don't know what I can do about that since IIRC I needed to upgrade to udev104 for something else). So even if I added something to init.d/xdm to force it to wait longer before starting slim, I still have the problem of silent reboot/shutdown.

For #3, if I don't background slim local.start never exits but I do get verbose logout when shutting down/restarting from xfce which is what I want. However, because local.start never exited (it's waiting for slim to "complete") I can't open any other login consoles. I also don't know what/if anything else gentoo inits following local.start that isn't being started (maybe this is why I can't open other consoles). And finally, because local.start is waiting for slim to detach/exit before completing, local.stop doesn't get executed when shutting down. IOW shutdown/reboots begins with local.start exiting and proceeds to shutdown/reboot from there, skipping local.stop entirely.

So, anyone have any idea how I can resolve this?

[timeBandit]

Try option #2 with a command to shutdown/kill Slim added to local.stop. That should close the login screen...?

FYI only (doesn't address silent shutdown), with option #1 you can edit the xdm init script's dependencies (after and/or need commands) to force xdm to run last. I once did this when designing a new silent bootsplash, to keep the splash up as long as possible, but quickly got sick of waiting. This change can be overwritten by updates to the init script so you have to watch for that.
_________________
Plants are pithy, brooks tend to babble--I'm content to lie between them.
Super-short f.g.o checklist: Search first, strip comments, mark solved, help others.

[nixnut]

Moved from Installing Gentoo to Other Things Gentoo.
Not about getting gentoo installed, so moved here.
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered

talk is cheap. supply exceeds demand

[nordic bro]

[timeBandit]

[nordic bro]

Thanks for your help. I was all excited to try out "chvt 1" because I was sure that would finally fix things. Unfortunately it didn't.

I messed around all yesterday/last night trying to understand what's going on and after countless iterations I can't figure it out. I even reinstalled xdm to run slim through that in case there was something somewhere that needed xdm for this to work.

What happens (killing/not killing slim, with/without xdm, running/not running consolefont, and using chvt in local.stop) is that when I exit xfce I usually, but not always, stay stuck on tty7 (where X is/was running). I put "touch abc/xyz" before/after chvt in local.stop so even though it looks like something else is sporadically dropping me back to tty1, it appears chvt in local.stop is being executed. And shutdown msgs show local.stop being executed first (as it's supposed to be).

But whether chvt executes or I switch to tty1 myself during shutdown (to see if fbsplash is there even though I didn't get switched to it), fbsplash is always gone; just gentoo runscript text on full screen black background. One time I saw the msg 'fbsplash switched to state "off"' or something like that but that msg usually isn't there so aren't sure it's relevant.

Curiously, a few other times when I switched to tty1 myself during shutdown something popped me back over to tty7 right in the middle of shutting down. So I have no idea what's going on or how to control it.


This is how I'm set up:

using splash-utils 1.5.2

patched 2.6.21 (kernel.org) with 4200_fbsplash-0.9.2-r5.patch

create an init image using splash_geninitramfs and use this in grub.conf:

kernel /boot/... splash=verbose,fadein,theme:fbsplash CONSOLE=tty1 quiet
initrd /boot/.../fbsplash

run /etc/runlevels/boot/consolefont (but saw no change when I took that out)

I don't run any splash utils/services (fbcondecor whatever that is, no fbsplashd whatever that is, etc.)

/etc/conf.d/splash is mostly all commented out

start slim daemon from /etc/conf.d/local.start (or via xdm when that was installed)

When I boot up everything is perfect; and unless I have slim detach I likewise have a perfect fbsplash shutdown.

It could be suggested to "keep doing it that way then" but if I don't let slim detach I lose access to any other consoles; and also as you point out, everything subsequent to slim starting is inside slim's environment to an extent. Maybe that's not a bad thing, I don't know, but it does have affects such as emacs starting oddly if slim isn't detached - there could be other undesirable things happening that I'm not even aware of.

I've done a lot of googling; even considered putting fbsplash on all consoles so that no matter where shutdown occurred I'd have my image but IIRC that makes local.start/stop run at points in init that would require me to make a number of other changes. I haven't been getting anywhere reading fbsplash docs/web page or a gentoo page on "init" - do you know some other resources I can look at to understand how to make this work?

[nordic bro]

Unfreakinbelievable It's always the simple thing that gets overlooked - NO /etc/splash link!!

Because I wasn't detaching slim originally, and therefore fbsplash shutdown was no problem (as you explained why in another reply), I didn't think the theme link in /etc/splash was being used for anything so never bothered restoring it. Now that slim runs in daemon mode the missing link is why fbsplash was always gone.

I'm still having a problem with getting back to tty1/screen corruption but technically OP is solved.

Thanks for your time/help.

Mod - I don't see how to mark this "solved"; do I just retitle it with "solved" (so I know in the future)?

[tarpman]

[timeBandit]