bestcrypt init cript - strange behavior
Dear list members: I have the following problem using bestcrypt 1.5-x (1.5-7, 1.5-10, 1.5- 11) on SuSE 9.2 (2.6.8-24.11-default, bash-3.0-8.2). After running the '/ etc/init.d/bcrypt start' script I have /dev/bcrypt* files with these permissions: brw------- 1 root root 188, 0 2005-03-02 13:59 /dev/bcrypt0 brw------- 1 root root 188, 1 2005-03-02 13:59 /dev/bcrypt1 etc. The mknod command in the script is: for (( x=0 ; x<16 ; x++)) ; do mknod -m 666 /dev/bcrypt$x b $MAJOR $(( MINOR+x )) ; done According to this, I think the permissions should be: brw-rw-rw- 1 root root 188, 0 2005-03-02 14:37 /dev/bcrypt0 brw-rw-rw- 1 root root 188, 1 2005-03-02 14:37 /dev/bcrypt1 etc. What really strange is that if I run the script once more, the permissions are corrected. What is going on here? Anybody has a clue? On Suse 9.1 I had no this problem. Any help appreciated, IG
participants (1)
-
Gabor Istvan