From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: fun with nilfs_cleanerd
Date: Thu, 26 May 2011 11:10:07 +0200 [thread overview]
Message-ID: <201105261110.15660.dexen.devries@gmail.com> (raw)
Hi list,
in /etc/rc.d/rc.local I have a command starting cleanerd for root filesystem:
# /sbin/nilfs_cleanerd -c /etc/nilfs_cleanerd-root.conf /dev/sda3
At first I wanted a separate config for root filesystem, but now same was to be
used for both / and /home. So I've removed the metion of the config file, and
the command became:
# /sbin/nilfs_cleanerd -c /dev/sda3
(note the -c !)
...ended up with nilfs_cleanerd spewing countless errors into /var/log/syslog,
like:
May 26 11:05:08 coil nilfs_cleanerd[18902]: ��: unknown keyword
May 26 11:05:08 coil nilfs_cleanerd[18902]: cˮ���: unknown keyword
May 26 11:05:08 coil nilfs_cleanerd[18902]: A�;^C�S-�g^W�^Fɂ: unknown keyword
May 26 11:05:08 coil nilfs_cleanerd[18902]: too long line
nilfs_cleanerd using whole partition as the config file == fun! ;-)
--
dexen deVries
[[[↓][→]]]
For example, if the first thing in the file is:
<?kzy irefvba="1.0" rapbqvat="ebg13"?>
an XML parser will recognize that the document is stored in the traditional
ROT13 encoding.
(( Joe English, http://www.flightlab.com/~joe/sgml/faq-not.txt ))
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2011-05-26 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 9:10 dexen deVries [this message]
[not found] ` <201105261110.15660.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-05-26 10:03 ` fun with nilfs_cleanerd Ryusuke Konishi
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=201105261110.15660.dexen.devries@gmail.com \
--to=dexen.devries-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox