Return to Question

I start my VNC server via a @reboot vncserver & entry in my user's crontab.

But this seems to cause some problems since the cron environment is restricted. For examples see:

• Get Bash instead of /bin/sh in a VNC session started by cron
• Shutdown and reboot buttons not working in VNC session started by cron

So I would like to know a better way for starting a VNC server for a user under his account.

I start my VNC server via a @reboot vncserver & entry in my user's crontab.

But this seems to cause some problems since the cron environment is restricted. For examples see:

• Get Bash instead of /bin/sh in a VNC session started by cron
• Shutdown and reboot buttons not working in VNC session started by cron

So I would like to know a better way for starting a VNC server for a user under his account.

I start my VNC server via a @reboot vncserver & entry in my user's crontab.

But this seems to cause some problems since the cron environment is restricted. For examples see:

• Get Bash instead of /bin/sh in a VNC session started by cron
• Shutdown and reboot buttons not working in VNC session started by cron

So I would like to know a better way for starting a VNC server.

I start my VNC server via a @reboot vncserver & entry in my user's crontab.

But this seems to cause some problems since the cron environment is restricted. For examples see:

• Get Bash instead of /bin/sh in a VNC session started by cron
• Shutdown and reboot buttons not working in VNC session started by cron

So I would like to know a better way for starting a VNC server for a user under his account.