On 13 Jan 2014 at 6:28, poma wrote:
Date sent: Mon, 13 Jan 2014 06:28:42 +0100
From: poma
To: Community support for Fedora users
Subject:Re: ssh difference with Fedora 20
Send reply to: Community support for Fedora
Dropbear(dbclient) also works nicely,
$ time dbclient -i .dropbear/dropbear_priv -l poma raw
Last login: …
$ systemctl reboot -i
AUTHENTICATING FOR org.freedesktop.login1.reboot ===
Authentication is required for rebooting the system.
Authenticating as: poma
Password:
AUTHENTICATION COM
On 14-01-12 01:50:40, Michael D. Setzer II wrote:
> ...If the command has a reboot option, it just sits there. The remote
> machine does reboot, but the connection doesn't close? End up having
> to kill the process to get it to go on to the next line of the
> script to do the next machine.
Make
On Sun, 12 Jan 2014 00:51:49 -0700
Chris Murphy wrote:
> Then chances are it's this bug:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1023820
Yep. Any kind of session that logs in a different
user on my f20 system makes it hang just about forever
on the next reboot attempt with the stoopid "s
On 12.01.2014 09:20, Michael D. Setzer II wrote:
> First, Thanks for the quick reply. I had done some additional testing, and it
> appears that it actually was rebooting as I had thought. The log shows it
> shuts down a bunch of things, but then just sits there, so the connection was
> actually
On 12 Jan 2014 at 8:49, poma wrote:
Date sent: Sun, 12 Jan 2014 08:49:40 +0100
From: poma
To: Community support for Fedora users
Subject:Re: ssh difference with Fedora 20
> On 12.01.2014 07:50, Michael D. Setzer II wr
If this works quickly
sync && reboot -f
Then chances are it's this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1023820
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fe
On 12.01.2014 07:50, Michael D. Setzer II wrote:
> With Fedora 20, when I ssh into other machines using plink to run commands
> to do various things, it all works fine with one exception. If the command
> has
> a reboot option, it just sits there. The remote machine does reboot, but the
> conn
Last week I got 21 new machines for my classroom to replace the 8 year old
machine. Old machine had Fedora 17 with 1 having 18 and 1 with 19. That
all worked well, but installed Fedora 20 on the new machines in addition to
the Windows 7 the machine came with. Have run into 1 issue so far.
With
