I have a stubborn module that refuses to load from INSMOD_COMMANDS.
When booting this particular client, I quit to busybox, unmount proc, insert my
module, and call /etc/init.d/rcS again.
All is well until I configure the network device and ping the imageserver ip.
A steady, un-ending stream of "[: 3: unknown operand" is sent to STDOUT.
Sometimes it's "3", sometimes it's "9" or "99". Grep and strings haven't
yielded any clues..
It seems to be related to a process that is running while /proc is umounted
from under it (init or rcS?)
It's not a show stopper, but it makes me wonder what's happening, and if this
is the reason restarting the imaging process without rebooting isn't a
"supported" or "published" option.
Thanks,
William J. Kennedy
Odyssey Information Services
Linux Systems Admin
[EMAIL PROTECTED]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
