search for: johnz

There is a bug in Swat package samba-swat-3.0.2a-3mdk The password functions are not working: add user, change password, enable user. If you add or enable a user, the user will be disabled. You can check this by opening /etc/samba/smbpasswd file. Entry will look like: johnz:500:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX [DU?????????]:LCT-00000000: The 32 X indicates that user has been disabled. Workaround: You can work around this problem by using SMB utility smbpasswd from the command line. For example as root: smbpasswd -a johnz -- John Zo...

Author: johnz Repository: /hg/zfs-crypto/gate Revision: 6c99fd0d9e58a3d469b9e74cc470cbe9bd740d49 Log message: 6349906 libelfsign verification should not link to pkcs11_softtoken dynamically Files: update: usr/src/lib/pkcs11/pkcs11_softtoken/Makefile.com

Hi, I have an R script that takes its input in the form of command-line parameters. It works fine, but R complains about every unknown arg with the "ARGUMENT %s ignored" message, and this goes to stdout instead of stderr because R_ConsoleFile isn't set yet. Is it really necessary to process all command line args before setting R_ConsoleFile? It seems that only Aqua systems care

Hi, I have an R script that takes its input in the form of command-line parameters. It works fine, but R complains about every unknown arg with the "ARGUMENT %s ignored" message, and this goes to stdout instead of stderr because R_ConsoleFile isn't set yet. Is it really necessary to process all command line args before setting R_ConsoleFile? It seems that only Aqua systems care

Hi, I'm a newbie trying to make an R program executable on UNIX, just like one would write an executable perl script by putting "#!/usr/bin/perl" in the first line, and so on. It seems, though, that this would only work if I use the "BATCH" command to tell R to execute the program in its first argument. This would have the unfortunately side-effect of dumping all