Search results for "change username Linux"

Re: [CentOS-devel] Website Version 2, next steps

by Andreas Rogge

Am 20.02.2011 20:25, schrieb Andrea Veri: > > Il giorno 18/feb/2011, alle ore 21.20, Ralph Angenendt ha scritto: > >> Am 18.02.11 18:23, schrieb Andrea Veri: >> >>> I agree with all the above. We just need to define which software to use >>> and then we should just roll up our sleeves and start making this real. >>> >>> Will wait the next step. >> >> Next step is swapping ideas around on how we can make sure to get a >> clean user database, > > Asking everyone to register again can be a working solution? :) > Yeah, but that would break the user's history and ACL. For me it seems too much Web 2.0 to be considered for Enterprise Linux :) > >> on how to make a central management "console" for >> that and on how to best plugin different applications into that. >> > > > why don't we simple use a normal LDAP istance? and why don't we have > a look at existing LDAP management consoles like Mango [1] or FAS? We need a self-service console which works for our existing applications and can - for example - solve "the wikiname problem" (i.e. different usernames based on the application accessed) We want to start out with a plain LDAP because it is widely supported by the applications we intend to use. We can still move somewhere else later as long as that one supports ldap-queries (i.e. IPA, Mango, whatever). The problem I see with FAS is that we'd need to change our applications to support it. For ldap it is usually just a few configuration-switches. > > Building one from scratch is definitely not an easy work, so it would be > the best to use an existing and tested solutions. Depends. There are centos people who are quite into ldap and while we need some weird stuff the whole thing is rather simple. Regards, Andreas -- Solvention Ltd. & Co. KG Egermannstr. 6-8 53359 Rheinbach Tel: +49 2226 158179-0 Fax: +49 2226 158179-9 http://www.solvention.de mailto:info@solvention.de

15 years, 1 month

Re: [CentOS-es] Ayuda con SAMBA

by Jose R. Lara

Saludos, Debes tener en cuenta que si tienes la opcion de guest desactivada es necesario tener una cuenta unix aparte de la de samba -----Original Message----- From: centos-es-bounces(a)centos.org [mailto:centos-es-bounces@centos.org] On Behalf Of Mario Villela Larraza Sent: Thursday, November 05, 2009 6:30 PM To: centos-es(a)centos.org Subject: [CentOS-es] Ayuda con SAMBA hola amiguos tengo de nuevo problemas con mi servidor samba, ya esta instalando y funcionando pero ahora mi problema es que no puedo agregar un usuario con permisos tengo entrada a mis archivos pero como invitado no puedo acceder con un usuario agregado ya con "smbuser" tengo idea que el problema esta en el archivo de configuracion, lo muestro aqui aver si aguien me puede ayudar con mi problema. muchas gracias de antemano # # 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. # A well-established practice is to name the original file # "smb.conf.master" and create the "real" config file with # testparm -s smb.conf.master >smb.conf # This minimizes the size of the really used smb.conf file # which, according to the Samba Team, impacts performance # However, use this with caution if your smb.conf file contains nested # "include" statements. See Debian bug #483187 for a case # where using a master file is not a good idea. # #======================= Global Settings ======================= [global] ## Browsing/Identification ### # Change this to the workgroup/NT-domain name your Samba server will part of workgroup = ARQUIS # server string is the equivalent of the NT Description field server string = Servidor De Archivos # 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 # What naming service and in what order should we use to resolve host names # to IP addresses ; name resolve order = lmhosts host wins bcast #### 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 ####### # "security = user" is always a good idea. This will require a Unix account # in this server for every user accessing the server. See # /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html # in the samba-doc package for details. security = user username map = /etc/samba/smbusers # You may wish to use password encryption. See the section on # 'encrypt passwords' in the smb.conf(5) manpage before enabling. encrypt passwords = true # 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(a)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 ########### # Is this machine able to authenticate users. Both PDC and BDC # must have this setting enabled. If you are the BDC you must # change the 'domain master' setting to no # ; domain logons = yes # # The following setting only takes effect if '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 ########## Printing ########## # If you want to automatically load your printer list rather # than setting them up individually then you'll need this # load printers = yes # lpr(ng) printing. You may wish to override the location of the # printcap file ; printing = bsd ; printcap name = /etc/printcap # CUPS printing. See also the cupsaddsmb(8) manpage in the # cupsys-client package. ; printing = cups ; printcap name = cups ############ 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 # Most people will find that this option gives better performance. # See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html # for details # You may want to add the following on a Linux system: # SO_RCVBUF=8192 SO_SNDBUF=8192 # socket options = TCP_NODELAY # The following parameter is useful only if you have the linpopup package # installed. The samba maintainer and the linpopup maintainer are # working to ease installation and configuration of linpopup and samba. ; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' & # Domain Master specifies Samba to be the Domain Master Browser. If this # machine will be configured as a BDC (a secondary logon server), you # must set this to 'no'; otherwise, the default behavior is recommended. # domain master = auto # 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 # The following was the default behaviour in sarge, # but samba upstream reverted the default because it might induce # performance issues in large organizations. # See Debian bug #368251 for some of the consequences of *not* # having this setting and smb.conf(5) for details. ; winbind enum groups = yes ; winbind enum users = yes # 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/mario/infra; browseable = no valid users = %S writable = yes # 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 ; share modes = no # 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 [printers] comment = All Printers browseable = no path = /var/spool/samba printable = yes guest ok = no read only = yes create 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 # A sample share for sharing your CD-ROM with others. ;[cdrom] ; comment = Samba server's CD-ROM ; read only = yes ; locking = no ; path = /cdrom ; guest ok = yes # The next two parameters show how to auto-mount a CD-ROM when the # cdrom share is accesed. For this to work /etc/fstab must contain # an entry like this: # # /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0 # # The CD-ROM gets unmounted automatically after the connection to the # # If you don't want to use auto-mounting/unmounting make sure the CD # is mounted on /cdrom # ; preexec = /bin/mount /cdrom ; postexec = /bin/umount /cdrom [Infra] comment = Directorio del servidor Infraestructura path = /home/mario/infra guest ok = no read only = Yes write list = administrador directory mask = 0755 create mask = 0644 aparte cree un archivo donde registro los usuarios que pueden acceder que se llama smbusers y este solo tiene el sigueiente texto usuario_linux = "usuario_windows" _______________________________________________ CentOS-es mailing list CentOS-es(a)centos.org http://lists.centos.org/mailman/listinfo/centos-es

16 years, 4 months

Re: [CentOS] OT: firefox question

by Skylar Thompson

I've noticed this as well, but it does seem to be limited to my FreeBSD desktop and none of my Linux/Windows systems, and also limited to sites doing HTTP "basic" authentication. It's pretty intermittent so it hasn't come to the point where I'm annoyed enough to delve into the underlying causes, though it does seem correlated with when I upgraded from Firefox 89->90 so going over the change log might be in order. On Fri, Jul 23, 2021 at 10:43:04AM -0500, Valeri Galtsev wrote: > Dear Experts, > > My question is OT, as it is related to firefox, not CentOS system per se. > Even more: my firefox runs on FreeBSD workstation. But I figured this list > have largest likelihood of having experts in firefox (as well as on other > things), so... > > My firefox behavior changed after one of recent updates.. > > When one logs in to website that is locked using web password (e.g., set in > .htacess/.htpasswd in apache), one gives username/password once. Then > firefox remembers that while firefox is running, and you don't have to give > credentials (though authentication does happen behind the scenes all the > time since). But not anymore for me at least on my (FreeBSD) workstation: in > the morning I discover firefox (though it had not been restarted) asks yet > again credentials to websites I have been logged to. As if firefox purges > credentials to websites after some period of time (or inactivity on those > websites). > > This stared happening not long ago after one of updates firefox is known to > release annoyingly often (as in: mozilla foundation forgot the meaning of > the word "release" which means well debugged code some time about decade > ago...). > > I tried to find relevant setting in GUI preferences to no avail (maybe it is > just me?), and hope, experts know deeper lying preferences, and may point me > to relevant one. > > All in all, I'm forced back onto my pursuit for replacement for firefox > browser... > > Thanks a lot for all your answers. And my apologies for rant (which I was > not able to separate due to my frustration...). > > Valeri > > -- > ++++++++++++++++++++++++++++++++++++++++ > Valeri Galtsev > Sr System Administrator > Department of Astronomy and Astrophysics > Kavli Institute for Cosmological Physics > University of Chicago > Phone: 773-702-4247 > ++++++++++++++++++++++++++++++++++++++++ > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos -- -- Skylar Thompson (skylar2(a)u.washington.edu) -- Genome Sciences Department (UW Medicine), System Administrator -- Foege Building S046, (206)-685-7354 -- Pronouns: He/Him/His

4 years, 8 months

Re: [CentOS-devel] [scl.org] CentOS SCLo SIG sync-up meeting on #centos-devel (2015-11-25)

by Fabian Arrotin

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 27/11/15 10:42, Dominic Cleal wrote: > On 24/11/15 12:15, Honza Horak wrote: >> * review new-SIG-member process (make approval part more >> concrete) > > I don't think this was discussed in the end, but how would I become > a member at the moment? As per > https://www.redhat.com/archives/sclorg/2015-November/msg00021.html > I'm interested in creating a new SCL under the SIG. > > Initially I'd like to start by creating a wiki page to plan it > under https://wiki.centos.org/SpecialInterestGroup/SCLo, which I > don't have permissions to do, and would assume I need to be a > member before I'd get edit access to that part of the wiki. > > It'll be a little while before I'm interested in building in CBS, > but I'll also raise bugs for access and to create tags which > appears to need SIG membership. > > Cheers, > So, For the koji/CBS access, we'll migrate tomorrow the authentication backend, so once done (all current accounts being migrated/tested/validated), we'll announce it publicly, and we'll change the documentation according to the new setup. So there is no need to create a bug report actually, but rather wait some days so that we can have migrated, and then create yourself your account. Then, once a week, we'll review the people who have asked to be member of a SIG group, and we'll sync with the SIG Chair so that he can confirm with a +1 or -1, and then "sponsor" the user in the according Group (for a +1). More infos to come (very) soon for that For wiki access, it's still using its own auth backend, so you have to create your username (FirstnameLastname as convention) and ask for permissions to be granted (through a mail to the centos-docs list : https://lists.centos.org/mailman/listinfo/centos-docs) Does that answer your question(s) ? - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlZe5RcACgkQnVkHo1a+xU6x9wCfZMF26P7romPSehJRbSmW0STx zb4An3yGle6mJPXObNzHZkvtrNCrzQ16 =q1au -----END PGP SIGNATURE-----

10 years, 3 months

Re: [CentOS] CentOS 6.8 and samba

by Philipoff, Andrew

> I have another samba server and upgraded it to samba4. testparm returns > clean with the old config (ROLE_DOMAIN_PDC) and starts up fine. smbclient > seems to work fine. > > The next thing now is to try and make it a domain member so it can auth > against AD. > > Thanks, Andrew, I appreciate the pointers. You might want to take a look at "Integrating Red Hat Enterprise Linux 6 with Active Directory". It's the best document I've seen on this topic. I found that Samba/Kerberos/Winbind is the most complete solution for attaching a Samba fileserver in my AD environment. https://access.redhat.com/sites/default/files/attachments/rhel-ad-integrati… SSSD is really the way to go if you're running Centos 7, take a look at "Red Hat Enterprise Linux 7 Windows Integration Guide": https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/pd… Below is my documentation on how to attach a RHEL/CentOS system to an Active Directory Domain using Samba/Kerberos/Winbind. This configuration will allow you to provide SMB file sharing and SSH logins for users in your AD domain. Note this works in my AD domain but there might be some additional settings required for your AD domain. Work closely with your AD domain administrator. The name of the example server in this document is server.example.com, substitute all values specific to your environment. Sample configuration files are included following these directions. The following packages should be installed: samba4, samba4-common, samba4-client, samba4-winbind, samba4-winbind-clients, krb5-workstation, openldap-clients 1. Set NTP to use the correct server for your Active Directory domain: system-config-time Set the primary NTP server to be your domain/forest NTP server NTP_IP_address 2. Make backups of and edit the following system configuration files: a. cp -p /etc/resolv.conf{,.bak} b. vi /etc/resolv.conf c. cp -p /etc/hosts{,.bak} d. vi /etc/hosts e. cp -p /etc/nsswitch.conf{,.bak} f. vi /etc/nsswitch.conf g. cp -p /etc/samba/smb.conf{,.bak} h. vi /etc/samba/smb.conf If you are editing a smb.conf file of a previously existing Samba fileserver, do not change the range value in the "idmap config * : range =" parameter i. cp -p /etc/krb5.conf{,.bak} j. vi /etc/krb5.conf 3. Start the smb and winbind services: a. /etc/init.d/smb start b. /etc/init.d/winbindd start Note that smb and winbind daemons need to be set to start up on boot. In addition, the appropriate TCP ports will need to open on the system firewall if you are deploying a SMB/CIFS fileserver. 4. Create a computer record in your Active Directory OU Computers container: For server.example.com create a computer record called server 5. Initialize Kerberos and attach it to the Active Directory domain: a. kinit username b. net ads join -w EXAMPLE.COM -U username 6. Verify the bind to AD is valid: a. net ads info b. net ads testjoin 7. Create a Kerberos /etc/krb5.keytab file: net ads keytab create -U username 8. Verify the contents of the Kerberos keytab file: klist -ke 9. Add a share that has access restricted to an Active Directory group: a. mkdir /data b. vi /etc/samba/smb.conf After the [homes}, section add the following text: [data] comment = Data Directory path = /data valid users = @"DOMAIN\AD_Group" writable = yes browseable = yes Substitute DOMAIN\AD_Group with an AD group that will be accessing this share. c. /etc/init.d/smb restart 10. Enable home directory creation a. system-config-authentication b. In the Advance Options tab, check the "Create home directories on the first login" checkbox. 11. Restrict SSH logins to a specific local and Active Directory groups Add this line to /etc/ssh/sshd_config: a. AllowGroups group_name Replace group_name with your local and AD group names. Note that the group names cannot have a space in the group name. Also make sure that at least one local group is added, otherwise you will not be able to SSH into your own server with a local account. 12. Restart your server Sample files: /etc/resolv.conf search example.com nameserver IP_address /etc/hosts 127.0.0.1 localhost.localdomain localhost IP_address server.example.com server /etc/nsswitch.conf passwd: files winbind shadow: files winbind group: files winbind hosts: files dns wins bootparams: nisplus [NOTFOUND=return] files ethers: files netmasks: files networks: files protocols: files rpc: files services: files netgroup: files publickey: nisplus automount: files aliases: files nisplus /etc/samba/smb.conf workgroup = example realm = EXAMPLE.COM server string = %h password server = * security = ads client use spnego principal = yes client use spnego = yes kerberos method = secrets and keytab server max protocol = SMB3 client signing = auto server signing = auto machine password timeout = 0 template shell = /bin/bash winbind use default domain = true winbind offline logon = false winbind refresh tickets = true idmap config * : range = 16777216-33554431 /etc/krb5.conf [logging] default = FILE:/var/log/krb5libs.log kdc = FILE:/var/log/krb5kdc.log admin_server = FILE:/var/log/kadmind.log [libdefaults] default_realm = EXAMPLE.COM default_keytab_name = /etc/krb5.keytab dns_lookup_realm = true dns_lookup_kdc = true ticket_lifetime = 24h forwardable = yes [realms] EXAMPLE.COM = { kdc = kdc.example.com.:88 kdc = IP_address admin_server = kdc.example.com kdc = IP_address } [domain_realm] .example.com = EXAMPLE.COM example.com = EXAMPLE.COM [kdc] profile = /var/kerberos/krb5kdc/kdc.conf [appdefaults] pam = { debug = false ticket_lifetime = 36000 renew_lifetime = 36000 forwardable = true krb4_convert = false } Andrew

9 years, 6 months

[CentOS] Samba 4.1.7 + CentOS 6.5 - Home's directory mounting in W7 + Roaming of Profils

by Pascal Blétard

Hello all, I progress slowly in my installation of Samba; but I'm confronted to two problems: 1) Is it possible to configure Samba (4.1.7) directly from GNU/Linux (CentOS 6.5) for automatically mount the user's home directory to "H:" when he connects to the domain ? 2) In addition, after that, I'll try to set up profiles' roaming. Here's my files: ---------------------------------------------- smb.conf (simplified after many tests) ---------------------------------------------- # Global parameters [global] #general naming workgroup = ADS realm = ADS.LOCAL netbios name = SERVER server string = File Server #logging log file = /usr/local/samba/var/log/%m.log max log size = 50 log level = 8 server role = active directory domain controller dns forwarder = 172.16.130.7 idmap_ldb:use rfc2307 = yes # These (uncommented) lines changes nothing # add user script = /usr/local/samba/sbin/add-user-script.sh %D %U %L #logon script = logon.bat #logon path = \\%L\\profile\\%U #logon drive = H: [netlogon] # this line isn't root preexec = /bin/bash /usr/local/samba/sbin/create-profile-directory.sh %D %U %L path = /usr/local/samba/var/locks/sysvol/ads.local/scripts read only = No #browsable=yes is for test only browsable=yes [sysvol] path = /usr/local/samba/var/locks/sysvol read only = No browsable=No [profile] comment = Roaming profiles path = /home/%D/profiles/ #browsable=yes is for test only browsable = yes writable = yes [homes] comment = %S's home root preexec = /bin/bash /usr/local/samba/sbin/create-home-directory.sh %D %S path = /home/%D/files/%S browsable = no ---------------------------------------------- create-home-directory.sh : ---------------------------------------------- #!/bin/bash if [ ! -e /home/$1/files/$2 ]; then mkdir -p /home/$1/files/$2 chmod 775 /home/$1/files/$2 chown $2:"Domain Users" /home/$1/files/$2 fi exit 0 ---------------------------------------------- create-profile-directory.sh : ---------------------------------------------- #!/bin/bash if [ ! -e /home/$1/profiles/$2 ]; then mkdir -p /home/$1/profiles/$2 chmod 775 /home/$1/profiles/$2 chown $2:"Domain Users" /home/$1/profiles/$2 pdbedit -u $2 -D "H:" -S "\\$3\\netlogon\\logon.bat" -h "$3\\$2 fi exit 0 ---------------------------------------------- add-user-script.sh: ---------------------------------------------- #!/bin/bash /usr/sbin/useradd -s /bin/false -d /home/$1/files/$2 -m $2 pdbedit -u $2 -D "H:" -S "\\$3\\netlogon\\logon.bat" -h "$3\\$2 ---------------------------------------------- logon.bat: ---------------------------------------------- net use h: %LOGONSERVER%\%USERNAME% ----------------------------------------------- Regards. Pascal Blétard

11 years, 9 months

Re: [CentOS] Linux newbie asks about sonypi on laptop

by Alex White

Ralph Loizzo wrote: > Collins Richey wrote: > >> On 7/30/05, Ralph Loizzo <ralphloizzo(a)sbcglobal.net> wrote: >> >> >>> Okay. I've been able to set my laptop's screen brighter by working with >>> the program spicctrl and the sonypi device. >>> >>> But everytime I boot, I login under my username then have to do the >>> following every time... >>> First I go into the bash terminal, then su because I can't do this under >>> my login name > >> >> As the following post indicated, you need to learn more about udev and >> how to setup devices using udev. >> >> However, as a workaround, your can put the commands you have to issue >> manually in /etc/rc.d/rc.local and they will be issued each time you >> boot. >> >> > Well I went ahead and changed rc.local instead of rc.sysinit (which i > had tried before) > and it worked! > > I will investigate udev at a later time, but at least now I can see my > screen! > > Thanks to you Collins and also to Shawn This sounds much like the nvidia issues that plagued many nvidia driver users. The issue involved udev and the nvidia driver some time ago. I know it was answered in the Fedora list several times you may want to google udev and nvidia. There is some syntax that allows you to keep certain devices. The problem was that you had to keep reinstalling the nvidia driver because udev would empty every reboot. To solve this the following was done as a result on google: cp -a /dev/nvidia* /etc/udev/devices/ chown root: /etc/udev/devices/nvidia* sooo..what you need to do is: cp -a /dev/sony* (perhaps /dev/sonypi?) /etc/udev/devices/ chown root: /etc/udev/devices/sony* (perhaps /dev/sonypi?) I think this would solve your problem...much more cleanly and without having to muddle around with any rc.local anything, which is not particularly ideal especially when you (and this may not be your case) have to have a something present early on and not at the very end of the entire boot process. HTH Alex White

20 years, 8 months

Re: [CentOS] Unable to mount SMB drive

by John Merritt

Benjamin Smith wrote: >Trying to keep this alive - I'm up against a wall here! > >I can use smbclient and not only see files, but actually download them (with >get) but I can't mount said Windows share locally to a drive - I universally >get a "permission denied" error. > >1) I've tried mounting via a line in fstab. > >2) I've tried smbmount with every option I could find. > >3) I've tried using mount with every option I could find. > >How could it work in smbclient with the same credentials, but not as an smb >mount? Is there something about how the Linux localhost is being announced, >perhaps? > >-Ben > >On Thursday 02 February 2006 18:45, Benjamin Smith wrote: > > >>I have a Windows Server 2003 system I'm trying to back up to a Linux host. >> >>when I access the share with smbclient, I can "see" the files (`ls` returns >> >> >a > > >>list of files, etc) >> >>smbclient -U shareuser //server/sharename password >> >>But, when I try to actually mount the drive, I get "permission denied" >> >> >errors > > >>trying to access the drive. (EG: using `df`) Running the following command >>takes about 10 seconds: >> >>smbmount //server/sharename /mnt/servername -o \ >>credentials=/path/to/credentials,ro >> >>I've also tried an alternate format: >> >>mount -t smbfs -o username=USERNAME //server/sharename /mnt/servername >> >>Same results both ways. I found a CentOS forum where somebody had problems >>with the RPM package, but retrograding to the package(s) he recommends >> >> >didn't > > >>change anything. >> http://www.centos.org/modules/newbb/viewtopic.php?topic_id=2307 >> >>I'm running the latest samba-client & samba-common on CentOS 4.2. SELinux is >>in warn mode. Here's the /var/log/messages when I mount: >> >>Feb 2 19:42:16 sol kernel: SELinux: initialized (dev smbfs, type smbfs), >> >> >uses > > >>genfs_contexts >>Feb 2 19:42:16 sol kernel: smb_retry: no connection process >>Feb 2 19:42:46 sol kernel: smb_add_request: request [c554bee0, mid=0] timed >>out! >>Feb 2 19:42:46 sol kernel: smb_delete_inode: could not close inode 2 >>Feb 2 19:42:46 sol kernel: SELinux: initialized (dev smbfs, type smbfs), >> >> >uses > > >>genfs_contexts >>Feb 2 19:42:46 sol mount.smbfs[21755]: [2006/02/02 19:42:46, 0] >>client/smbmount.c:send_fs_socket(410) >>Feb 2 19:42:46 sol mount.smbfs[21755]: mount.smbfs: entering daemon mode >>for service \\heliodorite.sunset.net\iissites, pid=21755 >> >>Running with debug=8 didn't provide much that was helpful. Any ideas where >> >> >to > > >>go from here? >> >>-Ben >>-- >>"The best way to predict the future is to invent it." >>- XEROX PARC slogan, circa 1978 >>_______________________________________________ >>CentOS mailing list >>CentOS(a)centos.org >>http://lists.centos.org/mailman/listinfo/centos >> >>-- >>This message has been scanned for viruses and >>dangerous content by MailScanner, and is >>believed to be clean. >> >> >> > > > Did you add the smbuser? smbpasswd -a John

20 years, 1 month

Re: [CentOS] INSTALLING UPDATES-PROXY PROBLEM

by Prabhpal S. Mavi

Hi Arun, 1. Is it CentOS 5.2? 2. Also disable CentOS plus repo by doing enable =0 in /etc/yum.repo/CentOSBase.repo, make sue you don't disable for CentOS & it is enable 3. Can you please copy above file from working system? 4. Can you now browse through lynx (Linux text browser) ? Thanks : Regards Sent from my IPhone > hey, iam extremly sorry for giving u trouble, > as u said i set the environment.... > this is the outcome after that > [BTIS@WORKSTATION3 ~]$ env | grep -i http_proxy > http_proxy=http://asomavarapu@actrec.gov.in:dbsa121@10.100.15.3:8080 > HTTP_PROXY=http://asomavarapu@actrec.gov.in:dbsa121@10.100.15.3:8080 > [BTIS@WORKSTATION3 ~]$ > > and this is the file of .bash_profile that i edited > > # .bash_profile > > # Get the aliases and functions > if [ -f ~/.bashrc ]; then > . ~/.bashrc > fi > > # User specific environment and startup programs > > PATH=$PATH:$HOME/bin > > export PATH > > export > http_proxy="http://asomavarapu@actrec.gov.in:dbsa121@10.100.15.3:8080 > " > export > HTTP_PROXY="http://asomavarapu@actrec.gov.in:dbsa121@10.100.15.3:8080 > " > > then i tried the command yum check-updates ,then this is the outcome > > [BTIS@WORKSTATION3 ~]$ yum check-update > Loaded plugins: fastestmirror, refresh-packagekit > Could not retrieve mirrorlist > http://mirrorlist.centos.org/?release=6&arch=i386&repo=os error was > 14: PYCURL ERROR 22 - "The requested URL returned error: 407" > Could not retrieve mirrorlist > http://mirrorlist.centos.org/?release=6&arch=i386&repo=centosplus error > was > 14: PYCURL ERROR 22 - "The requested URL returned error: 407" > Could not retrieve mirrorlist > http://mirrorlist.centos.org/?release=6&arch=i386&repo=extras error was > 14: PYCURL ERROR 22 - "The requested URL returned error: 407" > http://dl.google.com/linux/chrome/rpm/stable/i386/repodata/repomd.xml: > [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 407" > Trying other mirror. > Error: Cannot retrieve repository metadata (repomd.xml) for repository: > google-chrome. Please verify its path and try again > [BTIS@WORKSTATION3 ~]$ > > On Tue, Mar 27, 2012 at 3:39 PM, Prabhpal S. Mavi < > prabhpal(a)digital-infotech.net> wrote: > >> Hi Arun, >> >> Please understand and do as Johnny advised, it will fix your problem. >> Thanks >> > On 03/27/2012 03:47 AM, arun kumar wrote: >> >> sorry for not mentioning before that iam new to linux >> >> >> >> i have full access to internet, this is an educational institution, >> >> every >> >> one have there seperate username and pasword for login... >> >> so i used the my username and password in the yum.conf file.. >> >> >> >> i tried from GUI also like >> >> >> >> system->Administration-> software update ,then i got >> the >> >> folowing warning and error >> >> >> >> Software Update Viewer is running as a privileged user >> >> Package management applications are security sensitive. >> >> Running graphical applications as a privileged user should be avoided >> >> for >> >> security reasons. >> >> >> >> problem connecting to software source >> >> >> >> i also tried >> >> system->Administration->Add/Remove software >> >> >> >> iam not understanding what else to try >> > >> > <snip> >> > >> > If you do not have the Environment variable set for http_proxy, then >> > curl will not work. This seems like your problem to me. >> > >> > To see if you have http_proxy set as an environment variable, use this >> > command: >> > >> > env | grep -i http_proxy >> > >> > You need to check the above variable for both your "root user" and >> your >> > "local user" (local user's variables would be used if you are running >> > yum with sudo or su root ... root user would be used if you did "su - >> > root" or logged in directly as root. >> > >> > If the result is in caps, like this: >> > >> > HTTP_PROXY=http://my_username:mypassword@10.101.16.4:8080 >> > >> > Then curl might have an issue, so also add it in lower case like this: >> > >> > http_proxy="http://my_username:mypassword@10.101.16.4:8080" >> > >> > So, If you do not have a lower case "http_proxy=", then you would set >> it >> > in your root's ".bash_profile" file and your local user's >> > ".bash_profile" file. This is the line you would add to both users >> > .bash_profile: >> > >> > export http_proxy="http://my_username:mypassword@10.101.16.4:8080" >> > >> > After making the change, log out and back in to have the variables >> take >> > effect and then check them again with the grep command above ... >> > >> > Once you have the correct lower case variable set for "http_proxy=" >> for >> > both your normal local user and for root, you should be able to use >> yum >> > and curl. >> > >> > <snip> >> > >> >>> If the proxy server requires a username and password, add these to >> the >> >>> URL. To include the username |yum-user| and the password |qwerty|, >> add >> >>> these settings: >> >>> >> >>> |# The Web proxy server, with the username and password for this >> >>> account >> >>> http_proxy="http://yum-user:qwerty@mycache.mydomain.com:3128" >> >>> export http_proxy| >> >>> >> >>> *Example 5. Profile Settings for a Secured Proxy Server* >> >>> >> >>> [Note] The |http_proxy| Environment Variable >> >>> >> >>> The |http_proxy| environment variable is also used by |curl| and >> other >> >>> utilities. Although |yum| itself may use |http_proxy| in either >> >>> upper-case or lower-case, |curl| requires the name of the variable >> to >> >>> be >> >>> in lower-case. >> >>> >> > >> > >> > _______________________________________________ >> > CentOS mailing list >> > CentOS(a)centos.org >> > http://lists.centos.org/mailman/listinfo/centos >> > >> >> >> Thanks / Regards >> Prabhpal S. Mavi >> Email: prabhpal(a)digital-infotech.net >> Sent Through .Net Domain From iPhone >> >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> http://lists.centos.org/mailman/listinfo/centos >> > > > > -- > Arun Kumar Somavarapu > Project-JRF > Dr. Prasanna's lab > TMC, ACTREC > Navi Mumbai-410210 > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos > Thanks / Regards Prabhpal S. Mavi Email: prabhpal(a)digital-infotech.net Sent Through .Net Domain From iPhone

14 years

Re: Returning to - Re: [CentOS] Installing Java 1.4.2

by Will McDonald

I had to install the 1.4.2 SDK from Jpackage a while back for some friend's servers and vaguely documented it as I went. Here's the relevant bits with the profanities removed :) We'd already rsynced down the Jpackage repo so where I reference file:// for the baseurl you'll want to use http/ftp. PREPARING THE BUILD ENVIRONMENT Using Jpackage allows us to manage the installation of Java packages on RPM systems in a consistent fashion. Some packages will still require downloading of their sources due to licensing restictions but this source is used, in conjunction with Jpackage supplied SPEC files to build RPMs. http://www.jpackage.org/rebuilding.php First we need to create a build environment as a normal, non-root user. In this user's home area create the build tree as follows... rpm |-- BUILD |-- RPMS | |-- i386 | |-- i586 | `-- noarch |-- SOURCES |-- SPECS |-- SRPMS `-- tmp This command will create the build tree shown above... $ mkdir -p rpm/{BUILD,RPMS/{i386,i586,noarch},SOURCES,SPECS,SRPMS,tmp} Create an ~/.rpmmacros file, this will allow you to install SRPMs locally without b0rking the rest of the system, and add the following to it, changing the %packager details to your own... %_topdir %(echo ${HOME}/rpm) %_tmppath %{_topdir}/tmp %packager Firstname Lastname < your.address@here> As the repository files have already been rsync-ed down from the mirrors onto yumserv1/dev-rhe-a1 now we can setup Setup a Yum repository definition for the Jpackage repository. In /etc/yum.repos.d/ create a jpackge.repo and add the following... # Be sure to enable the distro specific repository for your distro below: # - jpackage-fc for Fedora Core # - jpackage-rhel for Red Hat Enterprise Linux and derivatives [jpackage-generic] name=JPackage (free), generic baseurl=ftp://yumserv1/jpackage/1.6/generic/free gpgcheck=0 gpgkey= http://www.jpackage.org/jpackage.asc enabled=1 [jpackage-rhel] name=JPackage (free) for Red Hat Enterprise Linux $releasever baseurl=ftp://yumserv1/jpackage/1.6/redhat-el-4.0/free/ gpgcheck=0 gpgkey=http://www.jpackage.org/jpackage.asc enabled=1 [jpackage-generic-nonfree] name=JPackage (non-free), generic baseurl= ftp://yumserv1/jpackage/1.6/generic/non-free/ gpgcheck=0 gpgkey=http://www.jpackage.org/jpackage.asc enabled=1 The firewalls on both yumserv1/dev-rhe-a1 and on webserv1 have been modified to allow limited FTP for the purposes of Yum updates. As root install the rpm-build and the Jpackage utils packages... # yum -y install rpm-build # yum -y install jpackage-utils INSTALLING JAVA Grab java-1.4.2-sun-1.4.2.10-1jpp.nosrc.rpm from your Yum repository and install it as your non-root user... $ cd ~/rpm/SRPMS $ wget ftp://yumserv1/jpackage/1.6/generic/non-free/SRPMS/java-1.4.2-sun-1.4.2.10-1jpp.nosrc.rpm $ rpm -ivh ~/rpm/SRPMS/java-1.4.2-sun-1.4.2.10-1jpp.nosrc.rpm Get the Java 1.4.2 SDK from http://java.sun.com/j2se/1.4.2/, specifically... http://javashoplm.sun.com/ECom/docs/Welcome.jsp?StoreId=22&PartDetailId=j2s… This has to be done via a browser because of Sun's click-through annoyance licensing. Download Linux Platform - Java(TM) 2 SDK, Standard Edition 1.4.2_10 self-extracting file j2sdk-1_4_2_10-linux-i586.bin . Copy this file into ~/rpm/SOURCES and then rpmbuild the RPM from the SPEC file which was installed when we installed java-1.4.2-sun-1.4.2.10-1jpp.nosrc.rpm... rpmbuild -ba ~/rpm/SPECS/java-1.4.2-sun.spec This will compile RPMs from the Java SDK and place them in ~/rpm/RPMS/i586. From these RPMs we want to install java-1.4.2-sun, java-1.4.2-sun-devel and an OS dependancy xorg-x11-deprecated-libs. As root carry out the following replacing $BUILDUSER with the non-root username we've been using for the builds... # yum -y install ~$BUILDUSER/rpm/RPMS/java-1.4.2-sun-1.4.2.10-1jpp.i586.rpm ~$BUILDUSER/rpm/RPMS/java-1.4.2-sun-devel-1.4.2.10-1jpp.i586.rpm Yum will take care of the xorg-x11 dependecy for you.

20 years, 1 month

Search results for query "change username Linux"