On Sat, 4 Jan 2014 19:42:16 -0600
Steven Ulrick meow8...@gmail.com wrote:
On Saturday, January 4, 2014, Sam Varshavchik mr...@courier-mta.com
wrote:
About ten hours after a reboot, a chance attempt to log in back to
the
server was rather rudely rejected with a:
System is booting up.
Steven P. Ulrick writes:
On Sat, 4 Jan 2014 19:42:16 -0600
Steven Ulrick meow8...@gmail.com wrote:
On Saturday, January 4, 2014, Sam Varshavchik mr...@courier-mta.com
wrote:
About ten hours after a reboot, a chance attempt to log in back to
the
server was rather rudely rejected with a:
On 01/08/14 20:29, Sam Varshavchik wrote:
Steven P. Ulrick writes:
On Sat, 4 Jan 2014 19:42:16 -0600
Steven Ulrick meow8...@gmail.com wrote:
On Saturday, January 4, 2014, Sam Varshavchik mr...@courier-mta.com
wrote:
About ten hours after a reboot, a chance attempt to log in back to
On 01/08/2014 04:29 AM, Sam Varshavchik issued this missive:
Steven P. Ulrick writes:
On Sat, 4 Jan 2014 19:42:16 -0600
Steven Ulrick meow8...@gmail.com wrote:
On Saturday, January 4, 2014, Sam Varshavchik mr...@courier-mta.com
wrote:
About ten hours after a reboot, a chance attempt to
Rick Stevens writes:
On 01/08/2014 04:29 AM, Sam Varshavchik issued this missive:
But if that's getting spuriously created, during a normal system state,
then something indeed must be creating it, in the wild.
Not going to be easy tracking it down. Perusing journalctl's man page,
there
On 01/08/2014 04:34 PM, Sam Varshavchik issued this missive:
Rick Stevens writes:
On 01/08/2014 04:29 AM, Sam Varshavchik issued this missive:
But if that's getting spuriously created, during a normal system state,
then something indeed must be creating it, in the wild.
Not going to be easy
On 01/09/14 10:09, Rick Stevens wrote:
I did some digging around and found the /run/nologin file is managed
by the program /usr/lib/systemd/systemd-user-sessions (invoked by
systemd-user-sessions.service).
FWIW, this issue has been reported as
Ed Greshko writes:
On 01/09/14 10:09, Rick Stevens wrote:
I did some digging around and found the /run/nologin file is managed
by the program /usr/lib/systemd/systemd-user-sessions (invoked by
systemd-user-sessions.service).
FWIW, this issue has been reported as
On Sat, 04 Jan 2014 22:35:12 -0500
Sam Varshavchik mr...@courier-mta.com wrote:
...
I yearn for the days of /etc/rc.d. If something strange was going on duri
ng system boot, a carefully crafted grep inevitably digs up a bunch of scrip
ts to sift through for the answers.
Now, there's all
About ten hours after a reboot, a chance attempt to log in back to the
server was rather rudely rejected with a:
System is booting up. See pam_nologin(8)
Connection closed by 192.168.0.2
A quick run back to the console revealed the existence of a ten hour old
/var/run/nologin file as the
On Saturday, January 4, 2014, Sam Varshavchik mr...@courier-mta.com wrote:
About ten hours after a reboot, a chance attempt to log in back to the
server was rather rudely rejected with a:
System is booting up. See pam_nologin(8)
Connection closed by 192.168.0.2
A quick run back to the
Steven Ulrick writes:
On Saturday, January 4, 2014, Sam Varshavchik URL:mailto:mrsam@courier-
mta.commr...@courier-mta.com wrote:
About ten hours after a reboot, a chance attempt to log in back to the
server was rather rudely rejected with a:
System is booting up. See pam_nologin(8)
12 matches
Mail list logo
