Comment # 10 on bug 966535 from patrick shanahan

(In reply to Dr. Werner Fink from comment #7)
> (In reply to patrick shanahan from comment #6)
> 
> Does this mean that
> 
>   systemctl enable wpa_supplicant.service
> 
> solves the problem?  Then a) there could be no
> 
>   %service_add_pre()                                                        
> 
>   %service_add_post()
>   %service_del_preun()
>   %service_del_postun()
> 
> and/or b) the presets below /usr/lib/systemd/system-preset/ do not include
> the enable line for wpa_supplicant.service.

no, but aleviates.  Whatever failed to *continue* to provide internet access
(wireless in *this* case) SHOULD HAVE CONTINUED.  And the open terminal should
not have been closed.

All of this causes GREATconcern when trying to maintain remote administration!

Something is WRONG and needs to be corrected.  The mere action of chaning
runlevel/active target/whatever it needs to be called MUST not close open
terminals and disable internet connection.  How else is remote administration
to even exist.(In reply to Dr. Werner Fink from comment #7)
> (In reply to patrick shanahan from comment #6)
> 
> Does this mean that
> 
>   systemctl enable wpa_supplicant.service
> 
> solves the problem?  Then a) there could be no
> 
>   %service_add_pre()                                                        
> 
>   %service_add_post()
>   %service_del_preun()
>   %service_del_postun()
> 
> and/or b) the presets below /usr/lib/systemd/system-preset/ do not include
> the enable line for wpa_supplicant.service.

No, it does not solve the problem of the active terminal being closed.  It does
continue internet connection, but why would this be NECESSARY when one already
had internet connection?  And why close the terminal?  Is remote administration
no longer a consideration?  SOMEONE has made a change in how systemd handles a
changed runlevel w/o ANY consideration for remote administration.  And if
notice was given, it DEFINITELY was not given where it would be seen by
interested parties.

systemd has changed and does not as presently constituted correctly handle
situations related to what one would consider normal operation or remote
administration.  systemd HAS changed w/o notice!