Re: How effectiate login.conf changes in console? ("ksh -l" does not)

2018-10-30 Thread Philip Guenther
On Mon, Oct 29, 2018 at 9:19 PM Joseph Mayer wrote: > On Tuesday, October 30, 2018 1:56 PM, Philip Guenther > wrote: > > On Mon, Oct 29, 2018 at 8:40 PM Joseph Mayer joseph.ma...@protonmail.com > > wrote: > > > > > After having changed /etc/login.conf I'd like to effectuate the > > > changes

Re: How effectiate login.conf changes in console? ("ksh -l" does not)

2018-10-30 Thread Joseph Mayer
On Tuesday, October 30, 2018 1:56 PM, Philip Guenther wrote: > On Mon, Oct 29, 2018 at 8:40 PM Joseph Mayer joseph.ma...@protonmail.com > wrote: > > > After having changed /etc/login.conf I'd like to effectuate the > > changes directly in the console, without doing a logout-relogin > > cycle. >

Re: How effectiate login.conf changes in console? ("ksh -l" does not)

2018-10-29 Thread Philip Guenther
On Mon, Oct 29, 2018 at 8:40 PM Joseph Mayer wrote: > After having changed /etc/login.conf I'd like to effectuate the > changes directly in the console, without doing a logout-relogin > cycle. > > Running "ksh -l" does *not* effectuate login.conf changes but only > re-runs the profile script

How effectiate login.conf changes in console? ("ksh -l" does not)

2018-10-29 Thread Joseph Mayer
Hi, After having changed /etc/login.conf I'd like to effectuate the changes directly in the console, without doing a logout-relogin cycle. Running "ksh -l" does *not* effectuate login.conf changes but only re-runs the profile script [1]. Running "login" asks for username and password which