tune2fs against a LVM (albeit formatted with ext4) is not the same as
tune2fs against ext4.
Could this possibly be a machine where uptime has outlived its usefulness?
On Thu, Apr 21, 2016 at 10:02 PM, Chris Murphy
wrote:
> On Tue, Apr 19, 2016 at 10:51 AM, Matt Garman
> wrote:
>
>
> ># rpm -qf
Chris Murphy wrote:
> What you should revert back to UEFI only, with Secure Boot enabled,
> and reinstall CentOS, deleting the previous partition/mount points
> including the BIOS Boot partition that was created for CentOS's
> bootloader.
> The gotcha is that with Secure Boot enabled, the CentOS
greetings.
centos 6.7 [current]
'disk utility' has started showing message;
WARNING: The partition is misaligned by 2560 bytes. This may
result in very poor performance. Repartitioning is suggested.
for sdc5 - /home partition.
/dev/sdc5 302243312 156348604 130534968 55% /home
/
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ.
Am 22.04.2016 um 12:40 schrieb g :
> greetings.
>
> centos 6.7 [current]
>
>
> 'disk utility' has started showing message;
>
> WARNING: The partition is misaligned by 2560 bytes. This may
> result in very poor performance. Repartitioning is suggested.
>
> for sdc5 - /home partition.
>
> /d
Hi,
I administer a postfix mail server on CentOS 6.
Now I want to setup another with similar configuration.
But the postgrey package is no longer available in Epel
for this CentOS release as I have seen now:
https://admin.fedoraproject.org/pkgdb/package/rpms/postgrey/
1. Will I have to make an u
Leon Fauster wrote:
> Am 22.04.2016 um 12:40 schrieb g :
>> centos 6.7 [current]
>> 'disk utility' has started showing message;
>>
>> WARNING: The partition is misaligned by 2560 bytes. This may
>> result in very poor performance. Repartitioning is suggested.
>> for sdc5 - /home partition.
>>
>>
On 23/04/16 02:13, Gabriele Pohl wrote:
> I administer a postfix mail server on CentOS 6.
> Now I want to setup another with similar configuration.
>
> But the postgrey package is no longer available in Epel
> for this CentOS release as I have seen now:
> https://admin.fedoraproject.org/pkgdb/pack
On 04/22/16 08:19, Leon Fauster wrote:
<<>>
> check it with:
>
> blockdev --getalignoff /dev/sd
>
> (if a '0' is returned, the partition is aligned)
>
===>
Leon,
thank you for reply.
]$ sudo blockdev --getalignoff /dev/sdc1
0
]$ sudo blockdev --getalignoff /dev/sdc2
0
]$ sudo blockdev --geta
On 04/22/2016 09:43 AM, g wrote:
]$ sudo blockdev --getalignoff /dev/sdc1
0
]$ sudo blockdev --getalignoff /dev/sdc2
0
]$ sudo blockdev --getalignoff /dev/sdc5
2560
]$ sudo blockdev --report /dev/sdc1
RORA SSZ BSZ StartSecSize Device
rw 256 512 4096 2048 8
On Sat, 23 Apr 2016 02:23:28 +1200
Peter wrote:
> On 23/04/16 02:13, Gabriele Pohl wrote:
> > I administer a postfix mail server on CentOS 6.
> > Now I want to setup another with similar configuration.
> >
> > But the postgrey package is no longer available in Epel
> > for this CentOS release as
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of Gabriele Pohl
> Sent: Friday, April 22, 2016 11:53 AM
> To: centos@centos.org
> Subject: [CentOS] output of "ls" (was: Re: Postgrey on CentOS 6)
>
> On Sat, 23 Apr 2016 02:23:28 +1200
On Fri, 22 Apr 2016 16:05:52 +
Richard Mann wrote:
> > What does the "." at the right side
> > of the attributes list mean?
> >
>
> Following the file mode bits is a single character that specifies
> whether an alternate access method such as an access control list
> applies to t
In the event that there are CentOS users making use of the EPEL owncloud
packages, but not following the EPEL mailing lists, please read the mail
below with regards to your installations.
Thanks
James
-- Forwarded message --
From: "James Hogarth"
Date: 22 Apr 2016 16:21
Subject:
Dear Experts,
I would like to ask everybody: what would you advise to use as a storage
cluster, or as a distributed filesystem.
I made my own research of what I can do, but I hit a snag with my
seemingly best choice, so I decided to stay away from it finally, and ask
clever people what they would
On 22/04/16 03:18 PM, Valeri Galtsev wrote:
> Dear Experts,
>
> I would like to ask everybody: what would you advise to use as a storage
> cluster, or as a distributed filesystem.
>
> I made my own research of what I can do, but I hit a snag with my
> seemingly best choice, so I decided to stay a
Hi Valeri
On Fri, Apr 22, 2016 at 10:24 PM, Digimer wrote:
> On 22/04/16 03:18 PM, Valeri Galtsev wrote:
>> Dear Experts,
>>
>> I would like to ask everybody: what would you advise to use as a storage
>> cluster, or as a distributed filesystem.
>>
>> I made my own research of what I can do, but
On Fri, 22 Apr 2016, Digimer wrote:
Then you would use pacemaker to manage the floating IP, fence
(stonith) a lost node, and promote drbd->mount FS->start nfsd->start
floating IP.
My favorite acronym: stonith -- shoot the other node in the head.
--
Paul Heinlein
heinl...@madboa.com
45°38' N,
On 22/04/16 04:40 PM, Paul Heinlein wrote:
> On Fri, 22 Apr 2016, Digimer wrote:
>
>> Then you would use pacemaker to manage the floating IP, fence
>> (stonith) a lost node, and promote drbd->mount FS->start nfsd->start
>> floating IP.
>
> My favorite acronym: stonith -- shoot the other node in t
What the heck is wrong with cron?
*/1 * * * * nobody /usr/bin/php /var/www/html/osticket/api/cron.php
in /etc/cron.d doesn't get executed at all (ran from console works of
course!). But the SAME file in /tmp runs flawlessly:
*/1 * * * * nobody /usr/bin/php /tmp/cron.php
It's CentOS7 on VPS wit
On Friday 22 of April 2016 11:40:33 PM Marcin Trendota wrote:
> What the heck is wrong with cron?
>
> */1 * * * * nobody /usr/bin/php /var/www/html/osticket/api/cron.php
>
> in /etc/cron.d doesn't get executed at all (ran from console works of
> course!). But the SAME file in /tmp runs flawlessly
On 04/22/2016 12:24 PM, Digimer wrote:
My requirements are:
This sounds like you want a cloud-type storage, like ceph or gluster.
I agree. I think either would work. A cluster with striping and
mirroring of volumes should fit all the requirements.
__
Why bother with */1? Wouldn't that be the same as just *?
On Apr 22, 2016 5:48 PM, "Marcin Trendota" wrote:
> On Friday 22 of April 2016 11:40:33 PM Marcin Trendota wrote:
> > What the heck is wrong with cron?
> >
> > */1 * * * * nobody /usr/bin/php /var/www/html/osticket/api/cron.php
> >
> > in
On Fri, Apr 22, 2016 at 4:40 AM, g wrote:
>
> =+=+=
> $ sudo fdisk -l /dev/sdc
> [sudo] password for geo:
>
> Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 byte
On Fri, Apr 22, 2016 at 4:11 AM, Timothy Murphy wrote:
> Chris Murphy wrote:
>
>> What you should revert back to UEFI only, with Secure Boot enabled,
>> and reinstall CentOS, deleting the previous partition/mount points
>> including the BIOS Boot partition that was created for CentOS's
>> bootload
On 04/22/2016 01:33 AM, Rob Townley wrote:
tune2fs against a LVM (albeit formatted with ext4) is not the same as
tune2fs against ext4.
tune2fs operates on the content of a block device. A logical volume
containing an ext4 system is exactly the same as a partition containing
an ext4 filesyste
On 04/21/2016 07:49 PM, Chandran Manikandan wrote:
Why it's happened like this environment and how to avoid it.
Generally the way to avoid it would be for your backup application to
fail if the destination does not exist, and alert the admin.
For instance, rsnapshot has the "no_create_root"
Oh and I can't stress enough to check for firmware updates. There's
metric tons of UEFI bugs. This little baby NUC has had 6 firmware
updates in 9 months. Some updates don't fix things I care about,
others do, and the changelogs aren't always really detailed when it
comes to thinks like user interf
On Fri, April 22, 2016 3:24 pm, Traiano Welcome wrote:
> Hi Valeri
>
>
> On Fri, Apr 22, 2016 at 10:24 PM, Digimer wrote:
>> On 22/04/16 03:18 PM, Valeri Galtsev wrote:
>>> Dear Experts,
>>>
>>> I would like to ask everybody: what would you advise to use as a
>>> storage
>>> cluster, or as a dist
On Fri, Apr 22, 2016 at 05:58:39PM -0400, Steven Ford wrote:
> Why bother with */1? Wouldn't that be the same as just *?
> On Apr 22, 2016 5:48 PM, "Marcin Trendota" wrote:
>
I had the same question. Plus, the man page says "'/' specifies
skips of the number's value through the range." That cou
On Friday 22 of April 2016 5:58:39 PM Steven Ford wrote:
> Why bother with */1? Wouldn't that be the same as just *?
That's for debugging. It'll be */5 for production purposes.
Anyway. It still doesn't work. Why?
--
Over And Out
MoonWolf
___
CentOS ma
Anything interesting in the logs?
sudo journalctl -xf _SYSTEMD_UNIT=crond.service
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Seemed strange is all. Can the nobody user read down into
/var/www/html/osticket/api? If it works in tmp, maybe permissions are the
issue.
On Apr 22, 2016 7:57 PM, "Marcin Trendota" wrote:
> On Friday 22 of April 2016 5:58:39 PM Steven Ford wrote:
> > Why bother with */1? Wouldn't that be the sam
On Saturday 23 of April 2016 10:08:54 AM Kahlil Hodgson wrote:
> Anything interesting in the logs?
>
> sudo journalctl -xf _SYSTEMD_UNIT=crond.service
Don't know.
[root@kohrin cron.d]# sudo journalctl -xf _SYSTEMD_UNIT=crond.service
-- Logs begin at śro 2015-12-02 22:34:16 CET. --
kwi 22 23:11:0
On Friday 22 of April 2016 8:10:04 PM Steven Ford wrote:
> Seemed strange is all. Can the nobody user read down into
> /var/www/html/osticket/api? If it works in tmp, maybe permissions are
> the issue.
As i said. sudo works as a charm. Cron rebels...
--
Over And Out
MoonWolf
_
On 4/22/2016 5:27 PM, Marcin Trendota wrote:
On Friday 22 of April 2016 8:10:04 PM Steven Ford wrote:
>Seemed strange is all. Can the nobody user read down into
>/var/www/html/osticket/api? If it works in tmp, maybe permissions are
>the issue.
As i said. sudo works as a charm. Cron rebels...
On 23 April 2016 at 10:25, Marcin Trendota wrote:
> Anything interesting in the logs?
> >
> > sudo journalctl -xf _SYSTEMD_UNIT=crond.service
>
> Don't know.
>
> [root@kohrin cron.d]# sudo journalctl -xf _SYSTEMD_UNIT=crond.service
>
...
> (/etc/cron.d/osticket-cron)
> kwi 22 23:28:01 vz471 c
If your script is failing, I would normally expect it to output some error
messages. Cron will email this to root by default. Maybe check
/var/spool/mail/root? Or set MAILTO="youremail address" at the top of your
cron script.
___
CentOS mailing list
Cen
On 04/22/16 05:40, g wrote:
<>
> suggestions for correcting above boundaries also appreciated.
>
> help needed and greatly appreciated.
>
===>
thank you all for replies. most helpful. now to decide which way to
format a new drive that i now have on order.
after reading replies, i feel easiest
On 04/21/2016 03:28 PM, Marcin Trendota wrote:
Also, you probably should specify tun+ instead of tun0, even if you
>think there will only be one tunnel up at any given time.
Specify where?
firewall-cmd --zone=home --add-interface=tun+
Beyond that, I can't really tell what firewalld is doing w
40 matches
Mail list logo
