The solution turned out to be simple: delete the misbehaving users and
re-create them. Now they can all ADD, DEL, MOVE, and COPY.
Rob
--
Я там, где ребята толковые,
Я там, где плакаты "Вперёд",
Где песни рабочие новые
Страна трудовая поёт.
On Thu, 10 Mar 2016, David Klann wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Rob,
Have you scoured logs for hints as to what might be breaking on this
machine? /var/log/messages, /var/log/syslog, etc., etc. (depending on
the specific OS you're running), and "sudo journalctl -b" on CentOS 7
and Debian Squeeze running systemd...
I'm eager to hear the solution to this one!
Best,
~David
On 03/10/2016 12:42 PM, Rob Landry wrote:
My understanding is that Rivendell users exist only within Rivendell;
the OS has no knowledge of them, only of the Linux user as whom the
software is running... and rdlogin doesn't change that. So... how would
file permissions be affected by logging into Rivendell as "Frilei"
instead of "user"? And which are the files in question?
I tried backing up and restoring the database, but it has no effect.
Rob
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iF4EAREIAAYFAlbh0GsACgkQZtxZ++32cNgjYAD/SyCmfip3NjbetA2Qz8eNpChN
p22Eiu9XzwQLH72dF+oBAKxNSwXWm4n7E2LKq90uoyHklF9YeDCnUyfsnqqYtX0m
=jP6S
-----END PGP SIGNATURE-----
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
