Re: RTC wakealarm write-only, still has 644 permissions

On Sunday 02 December 2007, Pavel Machek wrote:
> Anyway, with wildcarded dates, no-clobber is a problem -- because you
> need to kill the alarm after you waken up, or it will repeat.

And I've started to fix that problem.  Alarms need to
act only in oneshot mode for other reasons too.

- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- Re: RTC wakealarm write-only, still has 644 permissions
  - From: David Brownell <[email protected]>
- Re: RTC wakealarm write-only, still has 644 permissions
  - From: Pavel Machek <[email protected]>

Prev by Date: Re: [BUG 2.6.24-rc3-git6] SLUB's ksize() fails for size > 2048.
Next by Date: Re: Reproducible data corruption with sendfile+vsftp - splice regression?
Previous by thread: Re: RTC wakealarm write-only, still has 644 permissions
Next by thread: Re: RTC wakealarm write-only, still has 644 permissions
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]