1С:Предприятия в файловом варианте для OC Linux.
Установку
будем производить на чистой,
«свеже-установленной» системе Ubuntu 16.04
LTS.
Открываем
терминал сочетанием клавиш Ctrl+Alt+T.
Для
удобства ввода команд, чтобы каждый раз
не вводить sudo, включим учетную запись
рута простой установкой пароля для
пользователя root:
sudo
passwd root
система
попросит ввести новый пароль UNIX и потом
повторить его.
Теперь
можем ввести
su
и далее
вводим тот пароль, который установили
на предыдущем шаге и жмем Enter. Теперь мы
вошли в систему как суперпользователь
и у нас есть постоянный полный доступ
к системе для всех установок и настроек.
Предположим,
что у нас есть 2 компьютера с Ubuntu 16.04 LTS.
На одном из них будут лежать базы данных
(назовем его «сервером»), на другом
просто будем запускать 1С (назовем его
«клиентом») и стучаться в базы на сервере.
Настройки и
установки на серверной машине
Для
сетевой версии 1С необходимо «шарить»
базы по сети. В отличии от операционных
систем семейства Windows, в Linux данная
возможность по умолчанию отсутствует
в системе.
Добавим
эту возможность - ставим SAMBA из репозиториев
Ubuntu:
apt-get
install samba
Командой
smbstatus можно посмотреть какая версия
самбы установилась. На момент написания
данного мануала ставилась Samba version
4.3.9-Ubuntu.
Далее
необходимо создать папку, где будут
храниться базы 1С:
mkdir
/srv/share
Создадим
пользователя, от имени которого будут
идти все файловые операции с базами
данных:
useradd
user1c
Зададим
ему пароль такой же, как имя:
passwd
user1c
Для
корректной работы нам необходимо, чтобы
все папки и файлы в нашем хранилище баз
данных принадлежали пользователю
user1c. Сделаем это:
chmod
777 -R /srv/share
chown
user1c:user1c -R /srv/share
Следующим шагом будет настройка файловой
шары SAMBA. Отрываем на редактирование
конфигурационный файл:
gedit
/etc/samba/smb.conf
Откроется
текстовый редактор с конфигурационным
файлом. Нам необходимо заменить все его
содержимое на содержимое из нашего
файла smb.conf.
В
самой последней секции файла [share]
содержаться настройки открытия сетевого
доступа к нашей, созданной для баз
данных, папке. Если у вас базы будут
лежать в другом месте, то необходимо
скорректировать эту секцию файла —
прописать другой
полный путь в строке path.
Сохраним файл и закроем текстовый редактор и проверим,
что содержимое файла корректно для
нашей установленной версии Samba:
testparm
Система должна выдать ответ, в строчках
которого будет запись «Loaded services file OK.»
или сообщение, в какой строке файла
ошибка.
Если все настроено корректно, то
приступаем к установке 1С. Для начала
необходимо поставить требуемые пакеты,
от которых 1С зависит:
apt-get
install imagemagick
apt-get
install unixodbc
apt-get
install libgsf-bin
apt-get
install t1utils
apt-get install ttf-mscorefonts-installer
apt-get install ttf-mscorefonts-installer
Теперь
скачиваем с сайта http://users.v8.1c.ru
требуемый комплект файлов в зависимости
от разрядности используемой операционной
системы и ее менеджера пакетов. В нашем
случае для Ubuntu 16.04 LTS x86_64 это будет:
Клиент
1С:Предприятия (64-bit) для DEB-based Linux-систем
Cервер
1С:Предприятия (64-bit) для DEB-based Linux-систем
Устанавливать
сервер 1С для файловых версий обязательно,
несмотря на то, что лицензию на него мы
ставить не будем! Без сервера просто
ничего не заработает.
Для
установки скачанной версии распакуем
два архива в какую-то папку. У нас должно
получиться в ней 6 файлов:
1c-enterprise83-client_8.3.5-1625_amd64.deb
1c-enterprise83-client-nls_8.3.5-1625_amd64.deb
1c-enterprise83-common_8.3.5-1625_amd64.deb
1c-enterprise83-common-nls_8.3.5-1625_amd64.deb
1c-enterprise83-server_8.3.5-1625_amd64.deb
1c-enterprise83-server-nls_8.3.5-1625_amd64.deb
1c-enterprise83-ws_8.3.5-1625_amd64.deb
1c-enterprise83-ws-nls_8.3.5-1625_amd64.deb
В
более старших версиях платформы будет
8 файлов. В этом случае требуется удалить
файлы, в названии которых есть
"thin.client", чтобы не было лишних ошибок
при установке.
В
этой папке с файлами установки открываем
терминал и вводим команду
sudo
dpkg -i *.deb
При
установке не должно быть выдано никаких
сообщений с ошибками. Если говорит, что
что-то не установилось, то это необходимо
исправить.
Далее
необходимо примонтировать папку с
базами, чтобы 1С могла ее использовать
от имени созданного пользователя user1c.
Для
этого создадим папку, в которую будем
монтировать:
mkdir
-p
/mnt/share/bases
Дадим
на нее права для всех:
chmod
777 -R /mnt/share/bases
Теперь необходимо написать команду
монтирования файловой samba-шары в эту
папку. Для этого нам понадобится узнать
данные по текущему пользователю системы.
Откроем новый терминал по Ctrl+Alt+T и введем
команду
id
В ответе должны получить что-то вроде
uid=1000(user) gid=1000(user) .............
Подставим эти два значения в нижеследующую
команду
Выполним эту команду в терминале из под суперпользователя.
В результате мы должны в папке
/mnt/share/bases
увидеть
содержимое папки /srv/share.
Добавим в список баз 1С существующую
(не смотря на то, что самой базы еще нет
!!!) базу в папке /mnt/share/bases/myBase.
Запустим конфигуратор и подтвердим
желание создать новую информационную
базу в указанной папке.
Данная особенность создания базы
является способом обойти ошибку в версии
платформы под Linux. При обычном создании
новой базы, база не создается и выдается
сообщение "Ошибка создания информационной
базы!".
Теперь необходимо добавить монтирование
samba-шары с базами при загрузке компьютера.
Откроем на редактирование файл fstab:
gedit
/etc/fstab
В конфе файла с новой строки добавим
текст:
//127.0.0.1/share
/mnt/share/bases cifs
uid=1000,gid=1000,username=user1c,password=user1c,rw,iocharset=utf8,file_mode=0777,dir_mode=0777
0
0
Сохраним и закроем файл.
Теперь
необходимо подключить
скрипт my1C
к автозагрузке.
Для этого копируем файл my1C в папку
/etc/init.d, делаем его выполняемым chmod
+x /etc/init.d/my1C.
Далее выполняем команду
update-rc.d
my1C defaults 99
Теперь
можно перезагружать компьютер и
проверять, что в папке /mnt/share/bases
видно
содержимое папки /srv/share.
Настройки и
установки на клиентских машинах локальной
сети
На
клиентских машинах достаточно установить
платформу, как это указано выше, создать
папку для монтирования сетевой шары:
mkdir
-p /mnt/share/bases
И
внести
изменения в файл fstab:
gedit
/etc/fstab
добавить
строку:
//192.168.5.5/share
/mnt/share/bases cifs
uid=1000,gid=1000,username=user1c,password=user1c,rw,iocharset=utf8,file_mode=0777,dir_mode=0777
0
0
Указываем
ip-адрес серверной машины и uid, gid
соответственно для текущего пользователя
клиентской машины.
Автор: Вадим Ковыршин.
P.S. Как показала практика, такая установка 1С достаточна не стабильна, и нет не одной причины, по которой этот вариант можно использовать. Экономя на сетевой версии 1С мы получаем увеличение стоимости установки и обслуживания.
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
#======================= Global Settings =======================
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no
#### Networking ####
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes
#### Debugging/Accounting ####
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Cap the size of the individual log files (in KiB).
max log size = 1000
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
####### Authentication #######
# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
server role = standalone server
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam
obey pam restrictions = yes
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user
########## Domains ###########
#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set
#
# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U
# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u
# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g
############ Misc ############
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100
# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes
#======================= Share Definitions =======================
# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no
# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin
[share]
path = /srv/share
valid users = nobody
force group = user1c
force user = user1c
create mask = 0777
directory mask = 0777
read only = No
guest ok = Yes
inherit permissions = Yes
inherit owner = Yes
Автор: Вадим Ковыршин.
P.S. Как показала практика, такая установка 1С достаточна не стабильна, и нет не одной причины, по которой этот вариант можно использовать. Экономя на сетевой версии 1С мы получаем увеличение стоимости установки и обслуживания.
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
#======================= Global Settings =======================
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no
#### Networking ####
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes
#### Debugging/Accounting ####
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Cap the size of the individual log files (in KiB).
max log size = 1000
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
####### Authentication #######
# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
server role = standalone server
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam
obey pam restrictions = yes
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user
########## Domains ###########
#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set
#
# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U
# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u
# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g
############ Misc ############
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100
# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes
#======================= Share Definitions =======================
# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no
# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin
[share]
path = /srv/share
valid users = nobody
force group = user1c
force user = user1c
create mask = 0777
directory mask = 0777
read only = No
guest ok = Yes
inherit permissions = Yes
inherit owner = Yes
#!/bin/bash
# mount 1C share
while [ 1 = 1 ]
do
if ! [ -d /mnt/share/bases/myBase ] && ! [ -f /mnt/share/OK ]; then
/etc/init.d/samba start
mount -a
else
break
fi
done
if [ -d /mnt/share/bases/myBase ]; then
touch /mnt/share/OK
fi
if ! [ -d /mnt/share/bases/myBase ]; then
rm /mnt/share/OK
fi
# mount 1C share
while [ 1 = 1 ]
do
if ! [ -d /mnt/share/bases/myBase ] && ! [ -f /mnt/share/OK ]; then
/etc/init.d/samba start
mount -a
else
break
fi
done
if [ -d /mnt/share/bases/myBase ]; then
touch /mnt/share/OK
fi
if ! [ -d /mnt/share/bases/myBase ]; then
rm /mnt/share/OK
fi