Hi,
starting ReleaseCandidate2, I read that I can logon to NS shell using user, instead of user@domain.
Nice, shorter commands are better commands.
However, I seem to see that those are not quite the same, since I noticed something strange with crontab:
root@helium:~> $ crontab -u rolf -l
no crontab for rolf
root@helium:~> $ crontab -u rolf@mydomain -l
User rolf has no crontab, user rolf@mydomain does.
I thought those should be the same…?
Bug?
Addition: It’s even stranger:
when logging on as rolf, I see no crontab
when logging on as rolf@mydomain, I see no crontab
when logging on as root, I do see a crontab for rolf@mydomain
when logging on as root, I do not see a crontab for rolf
sorry, didn’t follow up on this one.
On my NS, there is an empty file cron.deny. (didn’t make it myself) Meaning all users should be allowed to use cron.
That’s consistent with the error when removing this file: then user rolf gets a message "you’re not allowed to use cron"
So, cron.deny or cron.allow isn’t the cause of this behaviour…
(jobs are actually run as user rolf, so that’s OK as well. It’s just about editing the crontab as user directly).
Is this reproducible by others?