From: Sergey Vlasov <vsu@altlinux.ru>
To: ALT Devel discussion list <devel@lists.altlinux.org>
Subject: Re: [devel] O_NOATIME behaviour changed in linux-2.6?
Date: Tue, 13 Jun 2006 20:31:55 +0400
Message-ID: <20060613163155.GF3206@master.mivlgu.local> (raw)
In-Reply-To: <20060613155340.GF10544@basalt.office.altlinux.org>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
On Tue, Jun 13, 2006 at 07:53:40PM +0400, Dmitry V. Levin wrote:
> On Tue, Jun 13, 2006 at 07:47:25PM +0400, Alexey Tourbin wrote:
> > On Tue, Jun 13, 2006 at 07:25:28PM +0400, Dmitry V. Levin wrote:
> [...]
> > > > Ещё хотелось бы использовать O_NOATIME, но это требует слишком больших
> > > > привилегий (CAP_FOWNER, как я понял из man capabilities).
> > > Да нет, вроде бы не требует.
> >
> > $ strace -o /dev/stdout -- perl -MFcntl=O_RDONLY,O_NOATIME -e 'sysopen FH, "/etc/passwd", O_RDONLY|O_NOATIME or die $!' |grep 'open(.*passwd'
> > open("/etc/passwd", O_RDONLY|O_LARGEFILE|O_NOATIME) = -1 EPERM (Operation not permitted)
> > Operation not permitted at -e line 1.
>
> А на 2.4.32 работает. Нужен комментарий ядерщиков.
2.4 вообще не поддерживает флаг O_NOATIME; похоже, нереализованные флаги
там просто игнорируются.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-06-13 16:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 10:06 [devel] sucap не работает Alexey Tourbin
2006-06-13 12:13 ` Dmitry V. Levin
2006-06-13 12:52 ` [devel] psec O_NOATIME Alexey Tourbin
2006-06-13 15:25 ` Dmitry V. Levin
2006-06-13 15:47 ` Alexey Tourbin
2006-06-13 15:51 ` Dmitry V. Levin
2006-06-13 16:25 ` Alexey Tourbin
2006-06-13 15:53 ` [devel] O_NOATIME behaviour changed in linux-2.6? Dmitry V. Levin
2006-06-13 16:31 ` Sergey Vlasov [this message]
2006-06-13 15:04 ` [devel] sucap не работает Alexey Tourbin
2006-06-13 15:30 ` [devel] sucap + execcap = Alexey Tourbin
2006-06-13 19:22 ` Alexey Tourbin
2006-06-14 22:12 ` Dmitry V. Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060613163155.GF3206@master.mivlgu.local \
--to=vsu@altlinux.ru \
--cc=devel@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git