On 01/02/15 22:37, jdow wrote:
Nahhh. Unless 'chrony' has completely mucked up the NTP spec, it deals
with symmetrical propagation delays pretty well. It effectively
reocords when you sent the request, when the response arrived, and
what the server thought the time was to derive the relevant ske
On 2015-01-02 14:08, Nico Kadel-Garcia wrote:
On Fri, Jan 2, 2015 at 3:12 PM, Bob Goodwin wrote:
Only the servers are blocked from the internet since I figured they didn't
require a connection but now the question of time synchronization arises. In
fact my internet connection is derived from a
On 01/02/15 17:08, Nico Kadel-Garcia wrote:
my internet connection is derived from a satellite connection which has
>a system delay on the order of 800 ms. I would think that would offset me
>from the rest of the world by nearly one second if it matters ...
Nahhh. Unless 'chrony' has completely
On Fri, Jan 2, 2015 at 3:12 PM, Bob Goodwin wrote:
> Only the servers are blocked from the internet since I figured they didn't
> require a connection but now the question of time synchronization arises. In
> fact my internet connection is derived from a satellite connection which has
> a system
On 2 January 2015 at 13:12, Bob Goodwin wrote:
>
> On 01/02/15 14:08, Stephen John Smoogen wrote:
>
>>
>> The ntp server needs to be able to talk to some server on the network to
>> get time. The Fedora boxes might just be 'lucky' in keeping time if they
>> have no access either.
>>
>> ntpq -p on
On 01/02/15 14:08, Stephen John Smoogen wrote:
The ntp server needs to be able to talk to some server on the network
to get time. The Fedora boxes might just be 'lucky' in keeping time if
they have no access either.
ntpq -p on each of the hosts will see how they are keeping time.
Well it lo
On 2 January 2015 at 10:15, Bob Goodwin wrote:
> On 01/02/15 11:57, Akemi Yagi wrote:
>
>> On Fri, Jan 2, 2015 at 7:33 AM, Bob Goodwin
>> wrote:
>>
>> Jan 02 10:18:12 box10 kernel: CIFS VFS: cifs_mount failed w/return code =
>>> -113
>>>
>> According to /usr/include/asm-generic/errno.h, return
On 01/02/15 11:57, Akemi Yagi wrote:
On Fri, Jan 2, 2015 at 7:33 AM, Bob Goodwin wrote:
Jan 02 10:18:12 box10 kernel: CIFS VFS: cifs_mount failed w/return code =
-113
According to /usr/include/asm-generic/errno.h, return code -113 means
/* No route to host */.
Akemi
"No route to host" for S
On Fri, Jan 2, 2015 at 7:33 AM, Bob Goodwin wrote:
> Jan 02 10:18:12 box10 kernel: CIFS VFS: cifs_mount failed w/return code =
> -113
According to /usr/include/asm-generic/errno.h, return code -113 means
/* No route to host */.
Akemi
On 01/02/15 06:43, Tom H wrote:
On Thu, Jan 1, 2015 at 4:01 PM, Bob Goodwin wrote:
I ran a system update on an SL-7 server and that seems to have messed up
samba. I can ssh into the system but can't mount it as a samba share.
[root@box10 bobg]# mount //192.168.1.48/myshare /mnt/box48/
Passwo
On Thu, Jan 1, 2015 at 4:01 PM, Bob Goodwin wrote:
>
> I ran a system update on an SL-7 server and that seems to have messed up
> samba. I can ssh into the system but can't mount it as a samba share.
>
> [root@box10 bobg]# mount //192.168.1.48/myshare /mnt/box48/
> Password for bobg@//192.168.1.
On Thu, Jan 1, 2015 at 4:01 PM, Bob Goodwin wrote:
> I ran a system update on an SL-7 server and that seems to have messed up
> samba. I can ssh into the system but can't mount it as a samba share.
"I ran a system update" covers a vast potential variety of sins. I'm
assuming you used "yum", not "
I ran a system update on an SL-7 server and that seems to have messed up
samba. I can ssh into the system but can't mount it as a samba share.
[root@box10 bobg]# mount //192.168.1.48/myshare /mnt/box48/
Password for bobg@//192.168.1.48/myshare:
Unable to find suitable address.
This
13 matches
Mail list logo
