On 01/07/2021 12:26, Pro Turm wrote:
> And also, looks like he's mapping host /tmp to the container.
>
> Why?
>
> This seems to be the reason. I mapped the host /tmp to the dockers /tmp
> to preserve core damps when the docker container stops or is deleted. It
> seems /tmp is loved by
>
> And also, looks like he's mapping host /tmp to the container.
>
> Why?
This seems to be the reason. I mapped the host /tmp to the dockers /tmp to
preserve core damps when the docker container stops or is deleted. It seems
/tmp is loved by everyone (not only firebird) who does important
On 01/07/2021 10:43, Alex Peshkoff via Firebird-devel wrote:
> On 7/1/21 4:27 PM, Pro Turm wrote:
>>
>> If you use UID/GID in docker with same number as firebird group in
>> host,
>> probably you will not have problem.
>>
>>
>> No, I dont set/use anything explicitly in the docker
On 7/1/21 4:27 PM, Pro Turm wrote:
If you use UID/GID in docker with same number as firebird group in
host,
probably you will not have problem.
No, I dont set/use anything explicitly in the docker regarding UID/GID.
If docker is using install script for linux distro, different
>
> If you use UID/GID in docker with same number as firebird group in host,
> probably you will not have problem.
>
No, I dont set/use anything explicitly in the docker regarding UID/GID.
Am Do., 1. Juli 2021 um 15:08 Uhr schrieb Adriano dos Santos Fernandes <
adrian...@gmail.com>:
> On
On 01/07/2021 09:59, Pro Turm wrote:
> Could the cause for the problem be the following constellation:
> host <-> docker : both use the same FB ?
> I suspect that after quitting the docker, it might set the tmp/firebird
> in the above state.
> What mechanism should FB use, to prevent the above
Could the cause for the problem be the following constellation:
host <-> docker : both use the same FB ?
I suspect that after quitting the docker, it might set the tmp/firebird in
the above state.
What mechanism should FB use, to prevent the above situation ?
Am Do., 1. Juli 2021 um 14:48 Uhr
I have the same situation again. How can I find out, whats causes, i.e.
sets the tmp/firebird in this situation ?
*$ sudo ls -laR /tmp/firebird/tmp/firebird:total 44*
*drwxrwx--- 2 84 84 4096 Jun 30 21:56 .drwxrwxrwt 33 root
root 36864 Jul 1 14:44 ..-rw-rw 1 firebird
most probably the *84 *(It was *UID* sorry, so it has probably nothing to
do with *kauditd*) is a *bug* from a previous FB4.0Beta or similar
installation.
Even though I stop the firebird service, the process remained being
executed:
*84603870 603770 0 09:52 ?00:00:00
The install script has the following command
*ps -efaww | egrep "\<(firebird\$|[[:space:]])" | grep -v grep | grep -v -w
'\-path'*
which returns
*84603871 603870 0 09:52 ?00:00:00
/opt/firebird/bin/firebird*
Even though I had removed the */opt/firebird* before I executed the
On 6/30/21 11:42 AM, Pro Turm wrote:
/$ sudo ls -laR /tmp/firebird
/tmp/firebird:
total 44
drwxrwx--- 2 84 84 4096 Jun 29 20:38 .
drwxrwxrwt 31 root root 36864 Jun 30 10:42 ..
-rw-rw 1 firebird firebird 0 Jun 28 11:07 fb_init
-rw--- 1 root root 0
*$ sudo ls -laR /tmp/firebird/tmp/firebird:total 44drwxrwx--- 2 84
84 4096 Jun 29 20:38 .drwxrwxrwt 31 root root 36864 Jun 30
10:42 ..-rw-rw 1 firebird firebird 0 Jun 28 11:07
fb_init-rw--- 1 root root 0 Jun 28 11:07 fb_rename_guard*
Am Mi., 30. Juni
On 6/30/21 11:21 AM, Pro Turm wrote:
Hi,
Does anyone know the reason for the following?
/Operating system call access failed. Error code 20/
/
/
/ConfigStorage: Cannot initialize the shared memory region
operating system directive access failed
Not a directory/
/
/
Hi,
Does anyone know the reason for the following?
*Operating system call access failed. Error code 20*
*ConfigStorage: Cannot initialize the shared memory regionoperating
system directive access failedNot a directory*
*Authentication erroroperating system directive
14 matches
Mail list logo
