Hi all,
I've got a cron job that runs a mysqldump script, and the last part of
that script removes the oldest of the files in the backup_dir.
The pertinent part of the script is:
# delete aged backup files, keeping 60 nightlies and 45 (5 days of) hourlies
rm $(ls -1t $MySQL_BACKUP_DIR_nightl
On Mon, 20 Jan 2014 06:38:40 -0500, Tanstaafl wrote:
> The pertinent part of the script is:
>
> > # delete aged backup files, keeping 60 nightlies and 45 (5 days of)
> > hourlies rm $(ls -1t $MySQL_BACKUP_DIR_nightly/* | tail -n +61)
> > rm $(ls -1t $MySQL_BACKUP_DIR_hourly/* | tail -n +46)
>
On Sun, 19 Jan 2014 08:25:16 -0500, Tanstaafl wrote:
> > cron mails are sent from the user running the cron job, but some
> > programs have an option to set the address for any mails they send
> > (not their stdout that goes through cron). rkhunter is one of these.
>
> Yes, and I have set it, b
On 2014-01-20 6:51 AM, Neil Bothwick wrote:
On Mon, 20 Jan 2014 06:38:40 -0500, Tanstaafl wrote:
The pertinent part of the script is:
# delete aged backup files, keeping 60 nightlies and 45 (5 days of)
hourlies rm $(ls -1t $MySQL_BACKUP_DIR_nightly/* | tail -n +61)
rm $(ls -1t $MySQL_BACKUP_
Hi. I am having a problem booting using systemd and an initrd generated
by genkernel.
I get the message that says (may be slight paraphrase) that
/dev/mapper/linux--files-64--root does not appear to be a valid /, try
again.
Now in the gentoo guide to systemd, I did what I think it wanted me to
d
On 01/20/14 14:37, Tanstaafl wrote:
> On 2014-01-20 6:51 AM, Neil Bothwick wrote:
>> On Mon, 20 Jan 2014 06:38:40 -0500, Tanstaafl wrote:
>>
>>> The pertinent part of the script is:
>>>
# delete aged backup files, keeping 60 nightlies and 45 (5 days of)
hourlies rm $(ls -1t $MySQL_BACKUP
On 01/20/14 14:37, Tanstaafl wrote:
> On 2014-01-20 6:51 AM, Neil Bothwick wrote:
>> On Mon, 20 Jan 2014 06:38:40 -0500, Tanstaafl wrote:
>>
>>> The pertinent part of the script is:
>>>
# delete aged backup files, keeping 60 nightlies and 45 (5 days of)
hourlies rm $(ls -1t $MySQL_BACKUP
On Sun, Jan 19, 2014 at 10:57 PM, Alan McKinnon wrote:
> That's how it is supposed to work. nfs is a Unix filesystem, it obeys
> Unix user and permissions (unlike say VFAT or smbfs where it has to
> fudge these things). NFS will mount the filesystem using whatever is set
> on the server. You canno
After upgrade to "systemd" my /dev/ttyS0 shows up as: root:dialout ownership
and permission 600
When I change as root manually to: chown uucp:dialout /dev/ttyS0
chmod 666 /dev/ttyS0
after restart it goes back to previous setting: root:dialout 600
How to change it?
My VituralBox complain and wi
On 19/01/14 23:31, Neil Bothwick wrote:
> On Sat, 18 Jan 2014 23:45:00 +, Mick wrote:
>
>> This thread confused me. I have this in my system and I have not
>> changed the permissions from when it was installed:
>>
>> ls -la /usr/libexec/dbus-daemon-launch-helper
>> -rws--x--- 1 root messagebu
On 01/20/14 18:30, Joseph wrote:
> After upgrade to "systemd" my /dev/ttyS0 shows up as: root:dialout
> ownership and permission 600
>
> When I change as root manually to: chown uucp:dialout /dev/ttyS0
> chmod 666 /dev/ttyS0
>
> after restart it goes back to previous setting: root:dialout 600
> H
On 20/01/14 18:45, Alan McKinnon wrote:
> On 01/20/14 18:30, Joseph wrote:
>> After upgrade to "systemd" my /dev/ttyS0 shows up as: root:dialout
>> ownership and permission 600
>>
>> When I change as root manually to: chown uucp:dialout /dev/ttyS0
>> chmod 666 /dev/ttyS0
>>
>> after restart it goe
On 01/20/14 18:45, Alan McKinnon wrote:
On 01/20/14 18:30, Joseph wrote:
After upgrade to "systemd" my /dev/ttyS0 shows up as: root:dialout
ownership and permission 600
When I change as root manually to: chown uucp:dialout /dev/ttyS0
chmod 666 /dev/ttyS0
after restart it goes back to previous
On 01/20/14 18:12, Chris Stankevitz wrote:
> On Sun, Jan 19, 2014 at 10:57 PM, Alan McKinnon
> wrote:
>> That's how it is supposed to work. nfs is a Unix filesystem, it obeys
>> Unix user and permissions (unlike say VFAT or smbfs where it has to
>> fudge these things). NFS will mount the filesyst
On 01/20/14 10:02, Joseph wrote:
On 01/20/14 18:45, Alan McKinnon wrote:
On 01/20/14 18:30, Joseph wrote:
After upgrade to "systemd" my /dev/ttyS0 shows up as: root:dialout
ownership and permission 600
When I change as root manually to: chown uucp:dialout /dev/ttyS0
chmod 666 /dev/ttyS0
after
On 01/20/2014 06:02:33 PM, Joseph wrote:
On 01/20/14 18:45, Alan McKinnon wrote:
On 01/20/14 18:30, Joseph wrote:
After upgrade to "systemd" my /dev/ttyS0 shows up as: root:dialout
ownership and permission 600
When I change as root manually to: chown uucp:dialout /dev/ttyS0
chmod 666 /dev/ttyS
On 01/20/14 18:20, Helmut Jarausch wrote:
[snip]
Hi,
I have the same permissions and VirtualBox (4.3.6) runs just fine.
VirtualBox is picky about the permission of the hard-disk image (VDI
file)
There it likes group vboxusers and group r/w permissions.
Helmut
Maybe I should recomplile Virtu
On 01/20/14 19:41, Joseph wrote:
> On 01/20/14 18:20, Helmut Jarausch wrote:
> [snip]
>>
>>
>> Hi,
>>
>> I have the same permissions and VirtualBox (4.3.6) runs just fine.
>> VirtualBox is picky about the permission of the hard-disk image (VDI
>> file)
>> There it likes group vboxusers and group r/
On Mon, Jan 20, 2014 at 9:10 AM, Alan McKinnon wrote:
> Most NFS servers in the real world are thus file shares and permit
> read-only access to all users.
Alan,
Thank you for explaining this in english for me. I am a bit blown
away that it is taking me so long to figure out that NFS might not
On 01/20/14 19:55, Chris Stankevitz wrote:
> On Mon, Jan 20, 2014 at 9:10 AM, Alan McKinnon
> wrote:
>> Most NFS servers in the real world are thus file shares and permit
>> read-only access to all users.
>
> Alan,
>
> Thank you for explaining this in english for me. I am a bit blown
> away th
On Sat, 18 Jan 2014 17:02:15 -0500
gottl...@nyu.edu wrote:
> My main system is a dell latitude E6430s. I am embarrassed to say
> that, although I have had this system for a while, I just now realized
> that it has a build in webcam. What software do you recommend and
> what should I start readi
Hi people!
I finally managed to update my "@system" profile completly.
Now I want to update world, and I see that certain packages require
"python_single_target_python2_7" or "python_single_target_python3_2"
I don't know how to change my make.conf that everything fits, that I can
update my entire
On Mon, Jan 20, 2014 at 3:27 PM, Tamer Higazi wrote:
> Hi people!
>
> I finally managed to update my "@system" profile completly.
> Now I want to update world, and I see that certain packages require
> "python_single_target_python2_7" or "python_single_target_python3_2"
>
> I don't know how to cha
You were RIGHT!
I had to comment out at make.conf 2 lines (last line wasn't enough):
PYTHON_TARGETS and PYTHON_SINGLE_TARGET as well.
Thank you David!
Tamer
On 01/20/14 21:45, David Abbott wrote:
> Try commenting them out.
> [snip]
> Regards,
> David
>
On Mon, Jan 20, 2014 at 12:00 PM, Alan McKinnon wrote:
> Indeed. The original use-case for NFS is no longer relevant whereas the
> design for smb *is* what suits most folk.
Alan,
What can I say. Thank you for your explanation. You wrote exactly
the words I needed to hear. For some reason, it
On 01/20/14 19:49, Alan McKinnon wrote:
On 01/20/14 19:41, Joseph wrote:
On 01/20/14 18:20, Helmut Jarausch wrote:
[snip]
Hi,
I have the same permissions and VirtualBox (4.3.6) runs just fine.
VirtualBox is picky about the permission of the hard-disk image (VDI
file)
There it likes group vbo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
we are planning to upgrade our virtualization infrastructure in the
near future. We are currently looking at 2 Dell PowerEdge R720 or R715.
The hardware (more or less):
- - Intel Xeon E5-2650v2
- - 24+ GB RAM
- - H710/H710P RAID controller
-
On 01/21/14 04:31, Joseph wrote:
> On 01/20/14 19:49, Alan McKinnon wrote:
>> On 01/20/14 19:41, Joseph wrote:
>>> On 01/20/14 18:20, Helmut Jarausch wrote:
>>> [snip]
Hi,
I have the same permissions and VirtualBox (4.3.6) runs just fine.
VirtualBox is picky about the
On 01/20/14 23:23, Tamer Higazi wrote:
> You were RIGHT!
>
> I had to comment out at make.conf 2 lines (last line wasn't enough):
>
> PYTHON_TARGETS and PYTHON_SINGLE_TARGET as well.
>
> Thank you David!
The reason this works is that the PYTHON_TARGETS are maintained in the
portage profile. Yo
On 01/20/14 23:23, Tamer Higazi wrote:
> You were RIGHT!
>
> I had to comment out at make.conf 2 lines (last line wasn't enough):
>
> PYTHON_TARGETS and PYTHON_SINGLE_TARGET as well.
>
> Thank you David!
The reason this works is that the PYTHON_TARGETS are maintained in the
portage profile. Yo
On 01/21/14 08:11, Johann Schmitz (ercpe) wrote:
> Hi all,
>
> we are planning to upgrade our virtualization infrastructure in the
> near future. We are currently looking at 2 Dell PowerEdge R720 or R715.
>
> The hardware (more or less):
> - Intel Xeon E5-2650v2
> - 24+ GB RAM
> - H710/H710P RAID
> We use Dell servers exclusively and have for 15 years. I think we're up
> to 400+ physical boxes now and the number of Linux-compatibility issues
> in all that time is exactly zero :-)
That's good to hear.
> If Dell sold server-class hardware that wasn't 100% supported in Linux,
> their sales w
32 matches
Mail list logo
