On Jun 4, 2015, at 10:35 PM, Douglas D Germann Sr 76066@compuserve.com
wrote:
I have a Synology ds213j which since a recent update will not recognize the
line in the server.conf that reads group nobody.
On some versions of Linux (And similar) it'd be nogroup instead of nobody
Doug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/06/15 04:35, Douglas D Germann Sr wrote:
[...snip...]
Thu Jun 4 22:23:45 2015 setgid('nobody') failed: Operation not
permitted (errno=1)
Hi,
I'm just so puzzled by this error message. Can you please do these
two commands and provide the
Hi,
On Fri, Jun 05, 2015 at 11:03:58AM -0400, Douglas D Germann Sr wrote:
OTOH, if this is screwed up, might there be some other bug that could
affect operations or security of this production nas? I worry
Of course there could be bugs overall :-) - but generally speaking, if
they did not
On 06/05/2015 11:10 AM, Gert Doering wrote:
Hi,
On Fri, Jun 05, 2015 at 11:03:58AM -0400, Douglas D Germann Sr wrote:
OTOH, if this is screwed up, might there be some other bug that could
affect operations or security of this production nas? I worry
Of course there could be bugs overall
David--
On 06/05/2015 06:06 AM, David Sommerseth wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/06/15 04:35, Douglas D Germann Sr wrote:
[...snip...]
Thu Jun 4 22:23:45 2015 setgid('nobody') failed: Operation not
permitted (errno=1)
Hi,
I'm just so puzzled by this error
JJK hi--
On 06/04/2015 10:58 AM, Jan Just Keijser wrote:
Hi,
Douglas D Germann Sr wrote:
I have a Synology ds213j which since a recent update will not
recognize the line in the server.conf that reads group nobody.
If I comment out that line, it runs OK. (It still has the user nobody
Friends--
I have a Synology ds213j which since a recent update will not recognize
the line in the server.conf that reads group nobody.
If I comment out that line, it runs OK. (It still has the user nobody
line, uncommented.)
I have tried changing it to group nogroup and that does not help.
