SliTaz Forum
You are not logged in.
Pages: 1
Hi, I keep getting the following errors listed in my /var/log/messages file.
Sep 29 22:13:58 (none) daemon.err udevd[2292]: bind failed: Address already in use
Sep 29 22:13:58 (none) user.notice error binding udev control socket
Sep 29 22:13:58 (none) daemon.err udevd[2291]: error binding udev control socket
Sep 29 22:13:58 (none) user.notice error binding udev control socket
Sep 29 22:13:58 (none) daemon.err udevd[2292]: error binding udev control socket
Is this something to be concerned about? Thanks
Offline
I get those errors while connecting a usb stick : it isn't mounted automaticaly, but I can do it as root to see the content.
Would be fine to mount automaticaly !
@gdesilva
If you run [c]tail -f /var/log/messages[/c] and udev is constantly spewing the errors I'd be concerned.
I get them when booting up/shutting down or insert/remove usb flash drives.
@arno
I use this udev rule to automount flash drives.The mount point is either /media/LABEL or /media/usbhd-sdx-#
Remove the .txt extension and copy the rules file to /etc/udev/rules.d
Offline
Thanks, mojo, it works fine 
I've just uncommented the utf8 stuff.
Is there any way to unmount with a clic ? The "mount devices manager" doesn't unmount my usb drive...
I'm not motivated to figure it out.
Maybe you can hack it to do what you want.
Find out why mountbox is unable to umount flashdrive.
Start mountbox in xterm,read the output when you click the unmount button.
Could be adding some umount options to /usr/bin/mountbox with a text editor is all you need.
Perhaps there are processes accessing the files on the flashdrive you have to kill before you can unmount.
Use [c]fuser -m mountpoint[/c] to find,use pkill on result.
Good luck,if you figure it out share it with the rest of us 
Offline
@mojo
mountbox tries to umount /media/cdrom, although I selected my flashdrive, which is mounted on /media/Transcend
But I found that double-clicking on the line instead of only selecting it allows me to umount correctly
Thanks
@mojo - thanks for this. I get the errors only when I insert a usb device so I guess it is all good.
I could not download the attachment specified in your previous response - I get restricted access message.
Offline
User's have to be logged into forum to download attachments. Try again,link is good.
Offline
@mojo - thanks. Can downlaod now ;-)
Offline
Hi,
Thank's a lot mojo,
Your procedure works perfectly :-)
... pushed because it's actual
( HD installation from SliTaz 4.0 standard iso, Toshiba satellite 5200-711, 512 Mb RAM, Pentium IV 1,9 Ghz,
40 Go HDD)
Offline
@mojo:
Since you would be concerned if the message-log constantly spews the udev-errors:
I use Slitaz 4 as frugal install, booting bzImage and rootfs.gz from HD.
After finishing all the changes of the original system (booted with rootfs1-4.gz) I packed the system again using 'tazlito writeiso gzip'.
After reboot, udev informs about the missing /run/udev directory, so for another try I added the directory and added those directories in tazlito, too, to be packed.
Nonetheless, I receive udev errors like gdesilva constantly (beginning during the boot-up-process and keeping up), although my system works fine.
ps -a shows multiple udevd instances running, which might be the reason for the errors but I didn't find a hint searching the init-files.
So after your comment I am concerned to some degree...
Any idea anyone ?!?
Thanx in advance...
Offline
Pages: 1
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]