From: Cyril HAENEL <chaenel@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Strange behavior with shell redirection
Date: Fri, 18 Dec 2009 14:37:45 +0100 [thread overview]
Message-ID: <4B2B85A9.8010806@free.fr> (raw)
In-Reply-To: <200912180630.54828.minimod@morethan.org>
> What is the implementation of that "reboot"?
> Yours? Something else?
>
ls -l /sbin/reboot
lrwxrwxrwx 1 root root 14 Jul 14 12:12 /sbin/reboot ->
../bin/busybox
It's the busybox's reboot implementation
> It is very common that "reboot" does just exactly that, reboots.
> No file sync, no file closing, nothing but reboot.
>
> Try syncing the filesystem and unmounting it before rebooting.
> mount -o remount <no options> <device name>
> will flush the VFS buffers to disk if you don't have a "sync" available.
> umount <device name>
> often does not flush/sync the file system, it depends on the FS.
> So use both of the above commands -
>
In /etc/inittab, I have :
# Stuff to do before rebooting
null::shutdown:/usr/bin/killall klogd
null::shutdown:/usr/bin/killall syslogd
null::shutdown:/bin/umount -a -r
null::shutdown:/sbin/swapoff -a
The umount -a -r seem's to umount all mounted FS. But maybe for my jffs2
FS I also need to do a mount -o remount, I look at this, thank for the
idea !
But I am not convinced that is the problem, because the board can stay
alive for very long periodsof time, the log can reach several megabytes,
thus I can't believe there is not at least a small part of the previous
log at the next startup. I use jffs2 for that, if the FS is not
correctly unmounted because a power failure for example, files are safe
and contain at least the last version of the file before the power failure.
> As to your first question -
> Correct, wrong list; try a linux newbee forum.
>
I fact I am not a newbee at all in linux, if I asked my question here,
it's really because I now that the problem I have doesn't exist on my
laptop for example !!
Regards,
Cyril
--
Cyril Haenel
Registered Linux User #332632
next prev parent reply other threads:[~2009-12-18 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 12:10 [Buildroot] Strange behavior with shell redirection Cyril HAENEL
2009-12-18 12:30 ` Michael S. Zick
2009-12-18 13:37 ` Cyril HAENEL [this message]
2009-12-18 14:19 ` Michael S. Zick
2009-12-18 18:03 ` Thomas Petazzoni
2009-12-18 19:30 ` Cyril HAENEL
2009-12-18 20:31 ` Michael S. Zick
2009-12-18 23:13 ` Cyril HAENEL
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=4B2B85A9.8010806@free.fr \
--to=chaenel@free.fr \
--cc=buildroot@busybox.net \
/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.