From: "hubert.loewenguth" <hubert.loewenguth@thales-bm.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: cramfs and crontab timestamp
Date: Thu, 15 Jun 2006 18:04:26 +0200 [thread overview]
Message-ID: <4491850A.8000608@thales-bm.com> (raw)
In-Reply-To: <44917BF1.5070700@thales-bm.com>
[-- Attachment #1: Type: text/plain, Size: 2384 bytes --]
Hi
Just a little precision: the /etc "copy/mount" is done before having
start the cron process.
Thanks again if you have an idea.
hubert.loewenguth a écrit :
> hi to the community
>
> I'm not sure here is the good place for my question because it's not
> related to the ppc architecture, but i try.
> Here is my problem I don't understand:
> I have an embended linux 2.4.20 on a 8260 ppc with a cramfs root
> file-system I use since 1 year.
> Everything works fine.
> During the init process, the content of the /etc directory is copy in
> a tmpfs file system and then then a tmpfs file-system is mounted on
> /etc and fill with the old content.
> (thanks to that, I can replace after some files in the /etc by other
> specific files store in a little jffs part of the flash with the
> customer specific configurations /etc configuration files).
>
> Recently, I've decided to add cron to this platform and something very
> strange appear.
> My /etc/crontab file is very simple:
>
> -----------------------------------------------
> SHELL=/bin/sh
> PATH=/sbin:/bin:/usr/sbin:/usr/bin
> MAILTO=""
> HOME=/
>
> #test of cron
> * * * * * root echo date >>/tmp/essai
> -----------------------------------------------
>
> everything works fine when I boot on a nfs file-system.
> But nothing is done (/tmp/essai not created) if I boot on the cramfs
> file-system.
> And what is the only difference beetwen the two startup:........ the
> timestamp of the /etc/crontab (1/1/1970 for crontab coming from the
> cramfs)
>
> So I try something after having boot on cramfs:
> echo "#toto">>/etc/crontab
>
> And ones I have done this, the cron process start to work correctly,
> creating and editing the /tmp/essai.
> I know that cron verify if the /etc/crontab has changed every mn, so I
> think this is the reason it works after, but why does it not see the
> first crontab file ?
> It's juste like the 1/1/1970 timestamp of /etc/crontab make him
> invisible by cron.
>
> Does anyone having an idea or having already encounter this kind of
> problem ?
> I have find nothing on the web about this or a similar problem.
>
> Thanks for any help
>
>_______________________________________________
>Linuxppc-embedded mailing list
>Linuxppc-embedded@ozlabs.org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
[-- Attachment #2: hubert.loewenguth.vcf --]
[-- Type: text/x-vcard, Size: 285 bytes --]
begin:vcard
fn:Hubert Loewenguth
n:Loewenguth;Hubert
org:Thales Broadcast & Multimedia
adr:;;1 rue de l'hautil;Conflans Ste Honorine;;78700;France
email;internet:hubert.loewenguth@thales-bm.com
title:Software Engineer
tel;work:01-34-90-37-56
x-mozilla-html:TRUE
version:2.1
end:vcard
prev parent reply other threads:[~2006-06-15 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 15:25 cramfs and crontab timestamp hubert.loewenguth
2006-06-15 16:04 ` hubert.loewenguth [this message]
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=4491850A.8000608@thales-bm.com \
--to=hubert.loewenguth@thales-bm.com \
--cc=linuxppc-embedded@ozlabs.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.