Dotaz: spouštění programu z nasdíleného /disku/adresáře

[jarda1]

zdravím přítomné,

mám následující problém a dotaz,

sestavil jsem si domací server, použil jsem distribuci ubuntu 14.04 lts, systém běží na ssd, samotný nasdílený disk je v raid poli 2x1tb hdd, pro nasdílení jsem použil daemona sambu, samba jako taková normálně běží, disk mám připojen do adresáře /home/ takto: /home/disk_wd1tb dále následují různé adresáře tento disk jsem připojil do win7 na nasdílený disk přistupujeme ze dvou pc z win7, někdy já, někdy manželka, ta používá účetní program, ve kterém vychází aktualizace, po instalaci aktualizací, nebo spíše pří probíhající aktualizaci se něco stane a aktualizace přestane fungovat, při znovu spuštění programu se objeví chyba, že systém windows nemá přístup k určenému zařízení, cestě, nebo souboru. K přístupu k položce pravděpodobně nemáte patřičná oprávnění, samba jako taková normálně dál funguje, do všech složek nasdíleného disku můžu kopírovat soubory, vytvořit a mazat složky, vše funguje normálně, jen se nespouští ten účetní program aby to dále fungovalo, na serveru se přihlásím jako root a v řádku spustím chmod 777 -R /home/disk_wd1tb po tomto se program zase spustí, než nastane další aktualizace,

nevím, kde může být zakopaný pes, nejsem úplně znalec linux systémů, ale s něčím jsem si schopen poradit, díky za případnou radu a pomoc

Odpovědi

[NN]

Jak vypada tvoje aktualni konfigurace Samby?

[jarda]

.conf: # # 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 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 # Windows clients look for this share name as a source of downloadable # printer drivers [print$] comment = Printer Drivers path = /var/lib/samba/printers browseable = yes read only = yes guest ok = no # 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 [diskwd] comment = diskwd1tb path = /home/disk_wd1tb public = yes writable = yes create mask = 0777 directory mask = 0777 force user = nobody force group = nogroup

[j]

Na sambe si muzes zapnout logovani

nejak takhle

[share] ... # vfs objects = full_audit # # full_audit:prefix = %u|%I|%m|%S ## full_audit:success = all # full_audit:failure = all

Pak v logu (kdyz to povolis komplet) uvidis jak uspesny tak neuspesny akce (kazdou akci, takze to nezapomen vypnout). Osobne bych spis videl problem v tom, ze widle ...

Je dost mozny, ze ta tvoje appka neumi fungovat se sitovym diskem. A presto, ze to treba mas primontovany na nejaky pismeno, tak widle appce vesele poslou \\cosi\neco\nekde ... z cehoz se spousta appek podela.

[j]

Fok ... tady to zas neumi formatovat samo

[share]
...
#    vfs objects = full_audit
#
#    full_audit:prefix = %u|%I|%m|%S
##    full_audit:success = all
#    full_audit:failure = all

[Filip Jirsák]

Sdílené disky ve Windows se připojují k danému uživateli, jiný uživatel je nevidí. Sdílený disk máte pravděpodobně namapovnaý pod svým běžným uživatelským účtem, ale instalace se spouští pod administrátorským účtem, který ten disk namapovaný nemá. Řešením je spustit nějakého správce souborů nebo Průzkumník jako správce, namapovat si tam ten síťový disk a pak rovnou spustit instalaci/aktualizaci.

S Linuxem tohle nijak nesouvisí, je to čistě záležitost toho, jak Windows pracují s uživateli a se sdílením disků.

[jarda]

na serveru mám pro sambu samotnou vytvořeného účet uživatele "uzivatel", ktery je zapsan a pridan i v systemu (ubuntu) samotném ano, nasdílený disk je ve win namapovám pod účtem "uzivatel"

[jarda1]

tak jsem vyzkoušel jak píšete, odpojil jsem jednotku v total commanderu, znovu připojil, připojil jsem ji jako přihlášením "root", ale při provedení aktualizace nastala stejná chyba, nevím jestli jsem Vás pochopil, snad ano

[Filip Jirsák]

Zkuste Total Commander spustit jako správce a pak z něj pokračujte spuštěním té aktualizace.

[jarda1]

vyzkouším jak píšete win-uživatel je zároveň správce

aktualizaci takto spustit můžu, ale napřed musím spustit ten účetní program a v něm aktualizaci vyvolat, program spustím z total commanderu a v něm vyvolám aktualizaci

[pavele]

Odebral bych volby (nobody je v linuxu systémový uživatel):

force user = nobody
force group = nogroup

V linuxu bych vytvořil uživatele se stejným přihlašovacím jménem jako je ve Windows, shell /bin/false a domovský adresář /dev/null.

Pomocí smbpasswd nebo pdbedit -a bych nastavil stejné heslo jako ve Windows.

Přidal bych volby:

force user = windowsuzivatel
force group = windowsuzivatel
create mask = 0660
directory mask = 0770
# acl allow execute always = True
# oplocks = no
# acl check permissions = false
# level2 oplocks = no
# locking = no
# strict locking = no
# share modes = no

[jarda1]

Dik za info, zkusil jsem, mam misto usera nobody, uzivatele pro sambu (zkusil jsem i root uzivatele) ale mam porad stejny problem

zkusil jsem i spusteni jak psal kolega vyse

.exe soubor ma atribut 777, zkusil jsem i 775, po padu se atribut nemeni, je stejny, opravdu by me zajimalo co se deje a s cim.

[jekub]

problém asi není v sambě (jak psal Filip J. v jednom z prvních komentářů). Jako správce nemáte namapovanou jednotku.

1) spustit cmd jako správce (Run as administrator)

2) namapovat co je potřeba (net use ...)

3) spustit program a aktualizaci