Hi
I think this is fixed in future rsync versions. For Ubuntu 14.04, exclude
ALL compression when rsyncing, e.v. chancve -az to -a.
Regards,
Jan
On 11 January 2016 at 12:56, Tom Worley wrote:
> I can confirm I still get this error on Ubuntu 14.04 (all up to date)
> rsync:
> Both machines: 3.1.
7e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_114021@/log.gz
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504781/+subscriptions
>
> --
> Mailing list: https://launchpad.net/~aims
>
t;
> --
> Mailing list: https://launchpad.net/~aims
> Post to : a...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~aims
> More help : https://help.launchpad.net/ListHelp
>
--
.~.
/V\ Jan Groenewald
/( )\www.aims.ac.za
^^-^^
--
You received
Public bug reported:
On 12.04.5 64bit server running rsync pulling backups from a 14.04 64bit
laptop dies with "inflate returned -3" when using the -z flag on a
backup containing a large file (a VM image over 1G). Removing the -z
flag works around the issue.
See the Debian bug:
https://bugs.debia
@snapperkob:~#cat /var/run/sshd.pid
cat: /var/run/sshd.pid: No such file or directory
1 root@snapperkob:~#start ssh
ssh start/running, process 6842
0 root@snapperkob:~#cat /var/run/sshd.pid
6842
0 root@snapperkob:~#
On 6 November 2014 18:55, Jan Groenewald wrote:
> Bad example in previous post; h
hd -D
root 32329 0.0 0.0 8864 652 pts/9S+ 18:53 0:00 grep
--color=auto sbin/sshd
0 root@kontiki:~#
On 6 November 2014 18:38, Jan Groenewald wrote:
> Server and desktop 14.04:
>
> 0 root@kontiki:~#ps auxw|grep sshd:
> root 7361 0.0 0.1 111844 4072 ?
rks fine, but ideally using the init
> script should still work as long as it's still there.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1390012/+subscriptions
>
> --
> Mailing list: https://launchpad.ne
Confirmed on third installation now, two servers and a desktop.
** Changed in: openssh (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- "/etc/init.d/ssh stop" does not stop ssh server processes
+ "/etc/init.d/ssh stop" does not stop ssh server processes on 14.04
--
You rec
November 2014 18:36, Jan Groenewald wrote:
> 14.04 server installs.
>
>
> On 6 November 2014 18:27, Brian Murray wrote:
>
>> What release did you notice this on? It worked fine for me on Vivid.
>>
>> [ 8:26AM ] [ bdmurray@impulse:~ ]
>> $ sudo /etc/init.d/ss
** Package changed: ubuntu => openssh (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1390012
Title:
"/etc/init.d/ssh stop" does not stop ssh server processes
To manage not
ca.archive.ubuntu.com/ubuntu/ precise/main amd64
> Packages
> 100 /var/lib/dpkg/status
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1103656/+subscriptions
>
> --
> Mailing list: https://launchpad.net/~aims
>
ons about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+subscriptions
>
--
.~.
/V\ Jan Groenewald
/( )\www.aims.ac.za
^^-^^
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to s
Public bug reported:
Squid3 on Precise does not clean up its PID file, causing logrotate to
spit out an error each night when cron runs it. This is on a server where
we want squid3 installed and ready to go but not running by default.
0 root@rackspace:/etc/mysql#start squid3
squid3 start/runnin
cBookAir:/home/clint#
>
> Could you run 'apport-collect 1039627' so we can see more about the
> affected system? Also, what language do you have (echo $LANG)?
>
Yes, I've run apport. $LANG is en_ZA.UTF-8.
Please let me know anything else you need.
apport information
** Attachment added: "modified.conffile..etc.etckeeper.etckeeper.conf.txt"
https://bugs.launchpad.net/bugs/1039627/+attachment/3304912/+files/modified.conffile..etc.etckeeper.etckeeper.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Server
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1039627/+attachment/3304911/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
https://bugs.launchpa
apport information
** Tags added: apport-collected precise running-unity
** Description changed:
0 root@muizenberg:/etc/#vim /etc/etckeeper/ # choose VCS=git
0 root@muizenberg:/etc/#etckeeper init
c
bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1039627
>
> Title:
> etckeeper init with git gives error
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/etckee
bug
> report.
> https://bugs.launchpad.net/bugs/1039627
>
> Title:
> etckeeper init with git gives error
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1039627/+subscriptions
>
--
.~.
/V\ Jan
** Package changed: ubuntu => etckeeper (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
https://bugs.launchpad.net/bugs/1039627
Title:
etckeeper init with git gives error
To manage notifications about t
To clarify:
It looks as if REMOVING the line "auth optional pam_group.so" from the lucid
client FIXES this. Is there something wrong with that syntax?
Removing the line from /etc/pam.d/gdm.
It is still in common-auth and login.
--
gdm does not obey NIS settings for user groups
https://bugs.laun
Just to confirm this problem is specific to lucid.
The previous desktop images were jaunty, and I have just tested
that this problem does not exist on the jaunty client!
On the jaunty install (no trailing line in /etc/group, no gdm:optional
pam_group.so line.)
li...@senegal:~$ grep 192 /etc/yp.c
User liesl is in NIS group aimsadmrw, but shed does not get permissions with
normal
login. However after either ssh localhost or su - liesl she does have the
necessary group
permissions.
On lucid 64bit, LDAP client for passwords, NIS client for groups, NFS/autofs
mounted /home.
ii nis
23 matches
Mail list logo
