Hello list, ..
I noticed some strange behavior, that I could not resolve so far, regarding
cron and crontab.
[user@container]$ crontab -e
You (user) are not allowed to access to (crontab) because of pam
configuration.
While digging in, I created /etc/cron.allow and added ALL. The message
change
On Thu, 2014-10-23 at 06:18 +0200, István Király wrote:
> Hello list, ..
>
>
> I noticed some strange behavior, that I could not resolve so far,
> regarding cron and crontab.
>
>
> [user@container]$ crontab -e
> You (user) are not allowed to access to (crontab) because of pam
> configuration.
Hello Mike.
Host is Fedora 20 with kernel 3.16.4-200.fc20.x86_64
LXC: 1.0.6 compiled from latest release
Host is fedora with SELinux disabled.
Container was created with the fedora template but in an earlier version of
LXC.
I'm not sure what you mean by container version. Containers are also F
On Thu, 2014-10-23 at 17:17 +0200, István Király wrote:
> Hello Mike.
>
>
> Host is Fedora 20 with kernel 3.16.4-200.fc20.x86_64
>
>
> LXC: 1.0.6 compiled from latest release
Ooo??? LXC 1.0.6 is in the repositories. Any reason for not using the
repo based LXC rpms?
When you say "compiled f
Hello again.
Yes, I see now that LXC 1.0.6 is there as rpm, but that is the first time
since 0.8.0, and I started to use LXC 1.0.
I use my script called srvctl to control the creation and configuration of
containers.
https://github.com/LaKing/Fedora-scripts
It compiled with "autogen - configure
On Tue, 2014-10-28 at 23:08 +0100, István Király wrote:
> Hello again.
>
>
>
> Yes, I see now that LXC 1.0.6 is there as rpm, but that is the first
> time since 0.8.0, and I started to use LXC 1.0.
>
>
> I use my script called srvctl to control the creation and
> configuration of containers.
>
