below is not exactly answering ur question, but i am sharing it in case it helps.
here is how i chose to live in order to minimize suffering, and i did not change this setup for several years: 0. i login in text (no gui login). i think xdm is fundamentally a redundant concept that should not have existed as per occam's razor. 1. i use i3, and start it by `startx`. i can auto-start startx upon login, but i like it better this way, as i may not always want gui stuff. 2. for screen locking, i made an i3 binding that executes `i3lock` upon pressing `mod+del`. 3. if i wanted to auto-lock, or auto-run a screen saver, i use things like `xautolock`. but i no longer do it, bcoz i don't feel i really need it (occam's razor) -- it's just that i happened to do it in the past. nowadays, i have evolved to just not forget locking the screen when leaving my desk. i know not exactly answering ur xdm-specific question, but i hope it offered u another perspective that might take u closer to ur nerd singularity. rgrds, cm. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, December 10, 2019 2:27 AM, jdm <j...@jdm.myzen.co.uk> wrote: > Hi, > > Over the last couple of weeks my wifi connection net.wlp5s0 doesn't see > to want to connect at boot up (It used to be very fast but now taking > 1min +). Therefore XDM (login screen slim) takes a long time to start > up. And LXD daemon doesn't start at all. > > I have my rc.conf set to rc_parallel="YES" but if I set this to "NO" > then clamd seems to take an age to start up as well as the wireless. > > Is there a way I can get XDM to start quicker and leave the other > services to start up whilst logging in. I can then set rc_parrallel to > "NO" which I hope should ensure LXD starts correctly. > > It's only a minor gripe but feels like it's taking a long time to > login. At least if I can get into desktop I can change wallpaper, > themes and icons whilst my wireless decides to get a grip. > > Thanks > John
