Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delay before device becomes availiable #6

Closed
GoogleCodeExporter opened this issue Aug 21, 2015 · 1 comment
Closed

Delay before device becomes availiable #6

GoogleCodeExporter opened this issue Aug 21, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. run: modprobe compcache && mv /dev/compcache0 /dev/ramzswap0

What is the expected output? What do you see instead?
I expect to have a new device named /dev/ramzswap0. I actually get an error
claiming that /dev/compcache0 does not exist.


What version of the product are you using? On what operating system?
compcache-0.2 on Ubuntu Hardy


Please provide any additional information below.
sleep 1 seems to be enough to ensure that the device has been created.
However it would be nice if modprobe/insmod did not return until the device
has been created, as this avoids timing gotchas (sleep 0.01 is *sometimes*
enough).

Original issue reported on code.google.com by gma...@gmail.com on 13 Mar 2008 at 11:19

@GoogleCodeExporter
Copy link
Author

This was basically udev issue. use_compcache.sh script in compcache-0.3 now 
makes
sure we do swapon only after device node is created (using udevadm settle).

Original comment by nitingupta910@gmail.com on 16 Mar 2008 at 8:37

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant