How can I allow one user to su to another without allowing root access?How can I create an “su” only user (no SSH or SFTP) and limit who can “su” into that account in RHEL5?allow a user to run command as another user without any password promptAllow user act as root, so he does not need to use sudo each time?Our security auditor is an idiot. How do I give him the information he wants?How to sudo as another user, without specifying the usernameHow can I create an “su” only user (no SSH or SFTP) and limit who can “su” into that account in RHEL5?sudo su - <username> should be possible but sudo su - shouldn't be for sudo userDoes my Oracle DBA need root access?How can I implement ansible with per-host passwords, securely?Allow linux root user mysql root access without passwordsudo permissions without root accessHow to sudo another user without password

How is linear momentum conserved in circular motion?

Teferi's Time Twist and Gideon's Sacrifice

How do you transpose samples in cents?

"Correct me if I'm wrong"

Bent arrow under a node

How can I prevent a user from copying files on another hard drive?

Explicit song lyrics checker

What mathematical theory is required for high frequency trading?

How can a clan of females defend themselves in the ancient world against wandering bands?

Print the new site header

What is the highest power supply a Raspberry pi 3 B can handle without getting damaged?

Is there a term for the belief that "if it's legal, it's moral"?

Counterfeit checks were created for my account. How does this type of fraud work?

Time at 1 g acceleration to travel 100 000 light years

Is there any way to revive my Sim?

King or Queen-Which piece is which?

In the US, can a former president run again?

Is Newton's third law really correct?

How to write a nice frame challenge?

Unrecognized IC Package Style

How Hebrew Vowels Work

Understanding “en comprend”

Would a 7805 5 V regulator drain a 9 V battery?

Make symbols atomic, without losing their type



How can I allow one user to su to another without allowing root access?


How can I create an “su” only user (no SSH or SFTP) and limit who can “su” into that account in RHEL5?allow a user to run command as another user without any password promptAllow user act as root, so he does not need to use sudo each time?Our security auditor is an idiot. How do I give him the information he wants?How to sudo as another user, without specifying the usernameHow can I create an “su” only user (no SSH or SFTP) and limit who can “su” into that account in RHEL5?sudo su - <username> should be possible but sudo su - shouldn't be for sudo userDoes my Oracle DBA need root access?How can I implement ansible with per-host passwords, securely?Allow linux root user mysql root access without passwordsudo permissions without root accessHow to sudo another user without password






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








52















I'd like to allow certain users to su to another user account without having to know that account's password, but not allow access to any other user account (i.e. root).

For instance, I'd like to allow Tom the DBA to su to the oracle user, but not to the tomcat user or root.



I imagine this could be done with the /etc/sudoers file - is it possible? If so, how?










share|improve this question






























    52















    I'd like to allow certain users to su to another user account without having to know that account's password, but not allow access to any other user account (i.e. root).

    For instance, I'd like to allow Tom the DBA to su to the oracle user, but not to the tomcat user or root.



    I imagine this could be done with the /etc/sudoers file - is it possible? If so, how?










    share|improve this question


























      52












      52








      52


      23






      I'd like to allow certain users to su to another user account without having to know that account's password, but not allow access to any other user account (i.e. root).

      For instance, I'd like to allow Tom the DBA to su to the oracle user, but not to the tomcat user or root.



      I imagine this could be done with the /etc/sudoers file - is it possible? If so, how?










      share|improve this question
















      I'd like to allow certain users to su to another user account without having to know that account's password, but not allow access to any other user account (i.e. root).

      For instance, I'd like to allow Tom the DBA to su to the oracle user, but not to the tomcat user or root.



      I imagine this could be done with the /etc/sudoers file - is it possible? If so, how?







      linux security sudo






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jun 2 '09 at 15:26







      gharper

















      asked Jun 2 '09 at 15:13









      gharpergharper

      4,64642233




      4,64642233




















          4 Answers
          4






          active

          oldest

          votes


















          44














          Yes, this is possible.



          In /etc/sudoers the item immediately following the equals is the user that the command will be allowed to execute as.



          tom ALL=(oracle) /bin/chown tom *


          The user (tom) can type sudo -u oracle /bin/chown tom /home/oracle/oraclefile






          share|improve this answer




















          • 5





            This would allow Tom to run commands as oracle, but not to actually become the oracle user

            – gharper
            Jun 2 '09 at 15:20






          • 11





            What about sudo -u oracle su -? That would give him a shell opened as the oracle user. Is that what you want?

            – Brent
            Jun 2 '09 at 15:23











          • +1 for that last comment, Brent. That would be my answer.

            – Annika Backstrom
            Jun 2 '09 at 15:26






          • 3





            Something like the following would work: sudo -u oracle -s or sudo -u oracle -i (-s for shell, -i for login - does a login shell). Unfortunately I don't know offhand what you would use in /etc/sudoers to limit the user, but given that you're allowing them shell access, you probably just want to do tom ALL=(oracle) ALL as someone else mentioned. If they can run a shell, you probably don't care about restriction the commands they can run.

            – Mark
            Jun 3 '09 at 1:59






          • 1





            Ideally, would you not want Tom to run commands as the oracle user, instead of becoming the oracle user? The distinction is slight, but it provides a great audit log without having to futz with using an audit shell.

            – Scott Pack
            Jun 16 '09 at 21:05


















          39














          Add to your /etc/sudoers something like



          tom ALL=(oracle) ALL


          Then user tom should be able to use sudo to run things as user oracle with the -u option, without letting tom



          I.e. getting a shell as user oracle (well, given that your sudo is new enough to have the -i option).



          sudo -u oracle -i





          share|improve this answer


















          • 5





            I had to use syntax tom ALL=(oracle)NOPASSWD:ALL to make sudo not to ask password

            – snowindy
            Dec 4 '15 at 5:45


















          8














          To ONLY provide the capabilities in the question, add the following to /etc/sudoers:



          tom ALL=(oracle) /bin/bash


          Then tom can:



          sudo -u oracle bash -i





          share|improve this answer






























            0















            For instance, I'd like to allow Tom the DBA to su to the oracle user, but not to the tomcat user or root.




            I needed to do this to a system recently and had a hard time finding my notes on the alternate setup i used years ago that also allowed the syntax su <user>. In my situation I needed to allow multiple users to su to a specific user.



            Create a group using addgroup <groupName> that other users will be able to su to without a password. Then add that group to each user that you want to be able to su to that user without a password:
            usermod -a -G <groupName> <userName> (or usermod -a -G oracle tom). The group changes might not take affect until next login.



            Note: In your case, you already have the group because oracle group would have been created when you made the oracle user with adduser oracle.



            Now edit /etc/pam.d/su and under the following:



            # This allows root to su without passwords (normal operation)
            auth sufficient pam_rootok.so


            ..add auth rule lines so the section looks like this:



            # This allows root to su without passwords (normal operation)
            auth sufficient pam_rootok.so
            auth [success=ignore default=1] pam_succeed_if.so user = <groupName>
            auth sufficient pam_succeed_if.so use_uid user ingroup <groupName>


            Replace <groupName> with oracle in this case. This will allow any user that is part of the <groupName> to su <groupName>



            Now tom can su oracle and if you need to give other users the same access, add them to oracle group.



            similar question here






            share|improve this answer





















              protected by Sven Dec 11 '14 at 22:49



              Thank you for your interest in this question.
              Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



              Would you like to answer one of these unanswered questions instead?














              4 Answers
              4






              active

              oldest

              votes








              4 Answers
              4






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              44














              Yes, this is possible.



              In /etc/sudoers the item immediately following the equals is the user that the command will be allowed to execute as.



              tom ALL=(oracle) /bin/chown tom *


              The user (tom) can type sudo -u oracle /bin/chown tom /home/oracle/oraclefile






              share|improve this answer




















              • 5





                This would allow Tom to run commands as oracle, but not to actually become the oracle user

                – gharper
                Jun 2 '09 at 15:20






              • 11





                What about sudo -u oracle su -? That would give him a shell opened as the oracle user. Is that what you want?

                – Brent
                Jun 2 '09 at 15:23











              • +1 for that last comment, Brent. That would be my answer.

                – Annika Backstrom
                Jun 2 '09 at 15:26






              • 3





                Something like the following would work: sudo -u oracle -s or sudo -u oracle -i (-s for shell, -i for login - does a login shell). Unfortunately I don't know offhand what you would use in /etc/sudoers to limit the user, but given that you're allowing them shell access, you probably just want to do tom ALL=(oracle) ALL as someone else mentioned. If they can run a shell, you probably don't care about restriction the commands they can run.

                – Mark
                Jun 3 '09 at 1:59






              • 1





                Ideally, would you not want Tom to run commands as the oracle user, instead of becoming the oracle user? The distinction is slight, but it provides a great audit log without having to futz with using an audit shell.

                – Scott Pack
                Jun 16 '09 at 21:05















              44














              Yes, this is possible.



              In /etc/sudoers the item immediately following the equals is the user that the command will be allowed to execute as.



              tom ALL=(oracle) /bin/chown tom *


              The user (tom) can type sudo -u oracle /bin/chown tom /home/oracle/oraclefile






              share|improve this answer




















              • 5





                This would allow Tom to run commands as oracle, but not to actually become the oracle user

                – gharper
                Jun 2 '09 at 15:20






              • 11





                What about sudo -u oracle su -? That would give him a shell opened as the oracle user. Is that what you want?

                – Brent
                Jun 2 '09 at 15:23











              • +1 for that last comment, Brent. That would be my answer.

                – Annika Backstrom
                Jun 2 '09 at 15:26






              • 3





                Something like the following would work: sudo -u oracle -s or sudo -u oracle -i (-s for shell, -i for login - does a login shell). Unfortunately I don't know offhand what you would use in /etc/sudoers to limit the user, but given that you're allowing them shell access, you probably just want to do tom ALL=(oracle) ALL as someone else mentioned. If they can run a shell, you probably don't care about restriction the commands they can run.

                – Mark
                Jun 3 '09 at 1:59






              • 1





                Ideally, would you not want Tom to run commands as the oracle user, instead of becoming the oracle user? The distinction is slight, but it provides a great audit log without having to futz with using an audit shell.

                – Scott Pack
                Jun 16 '09 at 21:05













              44












              44








              44







              Yes, this is possible.



              In /etc/sudoers the item immediately following the equals is the user that the command will be allowed to execute as.



              tom ALL=(oracle) /bin/chown tom *


              The user (tom) can type sudo -u oracle /bin/chown tom /home/oracle/oraclefile






              share|improve this answer















              Yes, this is possible.



              In /etc/sudoers the item immediately following the equals is the user that the command will be allowed to execute as.



              tom ALL=(oracle) /bin/chown tom *


              The user (tom) can type sudo -u oracle /bin/chown tom /home/oracle/oraclefile







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Jun 2 '09 at 15:24

























              answered Jun 2 '09 at 15:18









              Brent Brent

              14.7k166196




              14.7k166196







              • 5





                This would allow Tom to run commands as oracle, but not to actually become the oracle user

                – gharper
                Jun 2 '09 at 15:20






              • 11





                What about sudo -u oracle su -? That would give him a shell opened as the oracle user. Is that what you want?

                – Brent
                Jun 2 '09 at 15:23











              • +1 for that last comment, Brent. That would be my answer.

                – Annika Backstrom
                Jun 2 '09 at 15:26






              • 3





                Something like the following would work: sudo -u oracle -s or sudo -u oracle -i (-s for shell, -i for login - does a login shell). Unfortunately I don't know offhand what you would use in /etc/sudoers to limit the user, but given that you're allowing them shell access, you probably just want to do tom ALL=(oracle) ALL as someone else mentioned. If they can run a shell, you probably don't care about restriction the commands they can run.

                – Mark
                Jun 3 '09 at 1:59






              • 1





                Ideally, would you not want Tom to run commands as the oracle user, instead of becoming the oracle user? The distinction is slight, but it provides a great audit log without having to futz with using an audit shell.

                – Scott Pack
                Jun 16 '09 at 21:05












              • 5





                This would allow Tom to run commands as oracle, but not to actually become the oracle user

                – gharper
                Jun 2 '09 at 15:20






              • 11





                What about sudo -u oracle su -? That would give him a shell opened as the oracle user. Is that what you want?

                – Brent
                Jun 2 '09 at 15:23











              • +1 for that last comment, Brent. That would be my answer.

                – Annika Backstrom
                Jun 2 '09 at 15:26






              • 3





                Something like the following would work: sudo -u oracle -s or sudo -u oracle -i (-s for shell, -i for login - does a login shell). Unfortunately I don't know offhand what you would use in /etc/sudoers to limit the user, but given that you're allowing them shell access, you probably just want to do tom ALL=(oracle) ALL as someone else mentioned. If they can run a shell, you probably don't care about restriction the commands they can run.

                – Mark
                Jun 3 '09 at 1:59






              • 1





                Ideally, would you not want Tom to run commands as the oracle user, instead of becoming the oracle user? The distinction is slight, but it provides a great audit log without having to futz with using an audit shell.

                – Scott Pack
                Jun 16 '09 at 21:05







              5




              5





              This would allow Tom to run commands as oracle, but not to actually become the oracle user

              – gharper
              Jun 2 '09 at 15:20





              This would allow Tom to run commands as oracle, but not to actually become the oracle user

              – gharper
              Jun 2 '09 at 15:20




              11




              11





              What about sudo -u oracle su -? That would give him a shell opened as the oracle user. Is that what you want?

              – Brent
              Jun 2 '09 at 15:23





              What about sudo -u oracle su -? That would give him a shell opened as the oracle user. Is that what you want?

              – Brent
              Jun 2 '09 at 15:23













              +1 for that last comment, Brent. That would be my answer.

              – Annika Backstrom
              Jun 2 '09 at 15:26





              +1 for that last comment, Brent. That would be my answer.

              – Annika Backstrom
              Jun 2 '09 at 15:26




              3




              3





              Something like the following would work: sudo -u oracle -s or sudo -u oracle -i (-s for shell, -i for login - does a login shell). Unfortunately I don't know offhand what you would use in /etc/sudoers to limit the user, but given that you're allowing them shell access, you probably just want to do tom ALL=(oracle) ALL as someone else mentioned. If they can run a shell, you probably don't care about restriction the commands they can run.

              – Mark
              Jun 3 '09 at 1:59





              Something like the following would work: sudo -u oracle -s or sudo -u oracle -i (-s for shell, -i for login - does a login shell). Unfortunately I don't know offhand what you would use in /etc/sudoers to limit the user, but given that you're allowing them shell access, you probably just want to do tom ALL=(oracle) ALL as someone else mentioned. If they can run a shell, you probably don't care about restriction the commands they can run.

              – Mark
              Jun 3 '09 at 1:59




              1




              1





              Ideally, would you not want Tom to run commands as the oracle user, instead of becoming the oracle user? The distinction is slight, but it provides a great audit log without having to futz with using an audit shell.

              – Scott Pack
              Jun 16 '09 at 21:05





              Ideally, would you not want Tom to run commands as the oracle user, instead of becoming the oracle user? The distinction is slight, but it provides a great audit log without having to futz with using an audit shell.

              – Scott Pack
              Jun 16 '09 at 21:05













              39














              Add to your /etc/sudoers something like



              tom ALL=(oracle) ALL


              Then user tom should be able to use sudo to run things as user oracle with the -u option, without letting tom



              I.e. getting a shell as user oracle (well, given that your sudo is new enough to have the -i option).



              sudo -u oracle -i





              share|improve this answer


















              • 5





                I had to use syntax tom ALL=(oracle)NOPASSWD:ALL to make sudo not to ask password

                – snowindy
                Dec 4 '15 at 5:45















              39














              Add to your /etc/sudoers something like



              tom ALL=(oracle) ALL


              Then user tom should be able to use sudo to run things as user oracle with the -u option, without letting tom



              I.e. getting a shell as user oracle (well, given that your sudo is new enough to have the -i option).



              sudo -u oracle -i





              share|improve this answer


















              • 5





                I had to use syntax tom ALL=(oracle)NOPASSWD:ALL to make sudo not to ask password

                – snowindy
                Dec 4 '15 at 5:45













              39












              39








              39







              Add to your /etc/sudoers something like



              tom ALL=(oracle) ALL


              Then user tom should be able to use sudo to run things as user oracle with the -u option, without letting tom



              I.e. getting a shell as user oracle (well, given that your sudo is new enough to have the -i option).



              sudo -u oracle -i





              share|improve this answer













              Add to your /etc/sudoers something like



              tom ALL=(oracle) ALL


              Then user tom should be able to use sudo to run things as user oracle with the -u option, without letting tom



              I.e. getting a shell as user oracle (well, given that your sudo is new enough to have the -i option).



              sudo -u oracle -i






              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Jun 2 '09 at 15:26









              Kjetil JoergensenKjetil Joergensen

              5,06412217




              5,06412217







              • 5





                I had to use syntax tom ALL=(oracle)NOPASSWD:ALL to make sudo not to ask password

                – snowindy
                Dec 4 '15 at 5:45












              • 5





                I had to use syntax tom ALL=(oracle)NOPASSWD:ALL to make sudo not to ask password

                – snowindy
                Dec 4 '15 at 5:45







              5




              5





              I had to use syntax tom ALL=(oracle)NOPASSWD:ALL to make sudo not to ask password

              – snowindy
              Dec 4 '15 at 5:45





              I had to use syntax tom ALL=(oracle)NOPASSWD:ALL to make sudo not to ask password

              – snowindy
              Dec 4 '15 at 5:45











              8














              To ONLY provide the capabilities in the question, add the following to /etc/sudoers:



              tom ALL=(oracle) /bin/bash


              Then tom can:



              sudo -u oracle bash -i





              share|improve this answer



























                8














                To ONLY provide the capabilities in the question, add the following to /etc/sudoers:



                tom ALL=(oracle) /bin/bash


                Then tom can:



                sudo -u oracle bash -i





                share|improve this answer

























                  8












                  8








                  8







                  To ONLY provide the capabilities in the question, add the following to /etc/sudoers:



                  tom ALL=(oracle) /bin/bash


                  Then tom can:



                  sudo -u oracle bash -i





                  share|improve this answer













                  To ONLY provide the capabilities in the question, add the following to /etc/sudoers:



                  tom ALL=(oracle) /bin/bash


                  Then tom can:



                  sudo -u oracle bash -i






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Dec 11 '14 at 22:44









                  karimofthecropkarimofthecrop

                  9111




                  9111





















                      0















                      For instance, I'd like to allow Tom the DBA to su to the oracle user, but not to the tomcat user or root.




                      I needed to do this to a system recently and had a hard time finding my notes on the alternate setup i used years ago that also allowed the syntax su <user>. In my situation I needed to allow multiple users to su to a specific user.



                      Create a group using addgroup <groupName> that other users will be able to su to without a password. Then add that group to each user that you want to be able to su to that user without a password:
                      usermod -a -G <groupName> <userName> (or usermod -a -G oracle tom). The group changes might not take affect until next login.



                      Note: In your case, you already have the group because oracle group would have been created when you made the oracle user with adduser oracle.



                      Now edit /etc/pam.d/su and under the following:



                      # This allows root to su without passwords (normal operation)
                      auth sufficient pam_rootok.so


                      ..add auth rule lines so the section looks like this:



                      # This allows root to su without passwords (normal operation)
                      auth sufficient pam_rootok.so
                      auth [success=ignore default=1] pam_succeed_if.so user = <groupName>
                      auth sufficient pam_succeed_if.so use_uid user ingroup <groupName>


                      Replace <groupName> with oracle in this case. This will allow any user that is part of the <groupName> to su <groupName>



                      Now tom can su oracle and if you need to give other users the same access, add them to oracle group.



                      similar question here






                      share|improve this answer



























                        0















                        For instance, I'd like to allow Tom the DBA to su to the oracle user, but not to the tomcat user or root.




                        I needed to do this to a system recently and had a hard time finding my notes on the alternate setup i used years ago that also allowed the syntax su <user>. In my situation I needed to allow multiple users to su to a specific user.



                        Create a group using addgroup <groupName> that other users will be able to su to without a password. Then add that group to each user that you want to be able to su to that user without a password:
                        usermod -a -G <groupName> <userName> (or usermod -a -G oracle tom). The group changes might not take affect until next login.



                        Note: In your case, you already have the group because oracle group would have been created when you made the oracle user with adduser oracle.



                        Now edit /etc/pam.d/su and under the following:



                        # This allows root to su without passwords (normal operation)
                        auth sufficient pam_rootok.so


                        ..add auth rule lines so the section looks like this:



                        # This allows root to su without passwords (normal operation)
                        auth sufficient pam_rootok.so
                        auth [success=ignore default=1] pam_succeed_if.so user = <groupName>
                        auth sufficient pam_succeed_if.so use_uid user ingroup <groupName>


                        Replace <groupName> with oracle in this case. This will allow any user that is part of the <groupName> to su <groupName>



                        Now tom can su oracle and if you need to give other users the same access, add them to oracle group.



                        similar question here






                        share|improve this answer

























                          0












                          0








                          0








                          For instance, I'd like to allow Tom the DBA to su to the oracle user, but not to the tomcat user or root.




                          I needed to do this to a system recently and had a hard time finding my notes on the alternate setup i used years ago that also allowed the syntax su <user>. In my situation I needed to allow multiple users to su to a specific user.



                          Create a group using addgroup <groupName> that other users will be able to su to without a password. Then add that group to each user that you want to be able to su to that user without a password:
                          usermod -a -G <groupName> <userName> (or usermod -a -G oracle tom). The group changes might not take affect until next login.



                          Note: In your case, you already have the group because oracle group would have been created when you made the oracle user with adduser oracle.



                          Now edit /etc/pam.d/su and under the following:



                          # This allows root to su without passwords (normal operation)
                          auth sufficient pam_rootok.so


                          ..add auth rule lines so the section looks like this:



                          # This allows root to su without passwords (normal operation)
                          auth sufficient pam_rootok.so
                          auth [success=ignore default=1] pam_succeed_if.so user = <groupName>
                          auth sufficient pam_succeed_if.so use_uid user ingroup <groupName>


                          Replace <groupName> with oracle in this case. This will allow any user that is part of the <groupName> to su <groupName>



                          Now tom can su oracle and if you need to give other users the same access, add them to oracle group.



                          similar question here






                          share|improve this answer














                          For instance, I'd like to allow Tom the DBA to su to the oracle user, but not to the tomcat user or root.




                          I needed to do this to a system recently and had a hard time finding my notes on the alternate setup i used years ago that also allowed the syntax su <user>. In my situation I needed to allow multiple users to su to a specific user.



                          Create a group using addgroup <groupName> that other users will be able to su to without a password. Then add that group to each user that you want to be able to su to that user without a password:
                          usermod -a -G <groupName> <userName> (or usermod -a -G oracle tom). The group changes might not take affect until next login.



                          Note: In your case, you already have the group because oracle group would have been created when you made the oracle user with adduser oracle.



                          Now edit /etc/pam.d/su and under the following:



                          # This allows root to su without passwords (normal operation)
                          auth sufficient pam_rootok.so


                          ..add auth rule lines so the section looks like this:



                          # This allows root to su without passwords (normal operation)
                          auth sufficient pam_rootok.so
                          auth [success=ignore default=1] pam_succeed_if.so user = <groupName>
                          auth sufficient pam_succeed_if.so use_uid user ingroup <groupName>


                          Replace <groupName> with oracle in this case. This will allow any user that is part of the <groupName> to su <groupName>



                          Now tom can su oracle and if you need to give other users the same access, add them to oracle group.



                          similar question here







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Jun 2 at 11:27









                          jtlindseyjtlindsey

                          1691112




                          1691112















                              protected by Sven Dec 11 '14 at 22:49



                              Thank you for your interest in this question.
                              Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                              Would you like to answer one of these unanswered questions instead?



                              Popular posts from this blog

                              Wikipedia:Vital articles Мазмуну Biography - Өмүр баян Philosophy and psychology - Философия жана психология Religion - Дин Social sciences - Коомдук илимдер Language and literature - Тил жана адабият Science - Илим Technology - Технология Arts and recreation - Искусство жана эс алуу History and geography - Тарых жана география Навигация менюсу

                              Club Baloncesto Breogán Índice Historia | Pavillón | Nome | O Breogán na cultura popular | Xogadores | Adestradores | Presidentes | Palmarés | Historial | Líderes | Notas | Véxase tamén | Menú de navegacióncbbreogan.galCadroGuía oficial da ACB 2009-10, páxina 201Guía oficial ACB 1992, páxina 183. Editorial DB.É de 6.500 espectadores sentados axeitándose á última normativa"Estudiantes Junior, entre as mellores canteiras"o orixinalHemeroteca El Mundo Deportivo, 16 setembro de 1970, páxina 12Historia do BreogánAlfredo Pérez, o último canoneiroHistoria C.B. BreogánHemeroteca de El Mundo DeportivoJimmy Wright, norteamericano do Breogán deixará Lugo por ameazas de morteResultados de Breogán en 1986-87Resultados de Breogán en 1990-91Ficha de Velimir Perasović en acb.comResultados de Breogán en 1994-95Breogán arrasa al Barça. "El Mundo Deportivo", 27 de setembro de 1999, páxina 58CB Breogán - FC BarcelonaA FEB invita a participar nunha nova Liga EuropeaCharlie Bell na prensa estatalMáximos anotadores 2005Tempada 2005-06 : Tódolos Xogadores da Xornada""Non quero pensar nunha man negra, mais pregúntome que está a pasar""o orixinalRaúl López, orgulloso dos xogadores, presume da boa saúde económica do BreogánJulio González confirma que cesa como presidente del BreogánHomenaxe a Lisardo GómezA tempada do rexurdimento celesteEntrevista a Lisardo GómezEl COB dinamita el Pazo para forzar el quinto (69-73)Cafés Candelas, patrocinador del CB Breogán"Suso Lázare, novo presidente do Breogán"o orixinalCafés Candelas Breogán firma el mayor triunfo de la historiaEl Breogán realizará 17 homenajes por su cincuenta aniversario"O Breogán honra ao seu fundador e primeiro presidente"o orixinalMiguel Giao recibiu a homenaxe do PazoHomenaxe aos primeiros gladiadores celestesO home que nos amosa como ver o Breo co corazónTita Franco será homenaxeada polos #50anosdeBreoJulio Vila recibirá unha homenaxe in memoriam polos #50anosdeBreo"O Breogán homenaxeará aos seus aboados máis veteráns"Pechada ovación a «Capi» Sanmartín e Ricardo «Corazón de González»Homenaxe por décadas de informaciónPaco García volve ao Pazo con motivo do 50 aniversario"Resultados y clasificaciones""O Cafés Candelas Breogán, campión da Copa Princesa""O Cafés Candelas Breogán, equipo ACB"C.B. Breogán"Proxecto social"o orixinal"Centros asociados"o orixinalFicha en imdb.comMario Camus trata la recuperación del amor en 'La vieja música', su última película"Páxina web oficial""Club Baloncesto Breogán""C. B. Breogán S.A.D."eehttp://www.fegaba.com

                              What should I write in an apology letter, since I have decided not to join a company after accepting an offer letterShould I keep looking after accepting a job offer?What should I do when I've been verbally told I would get an offer letter, but still haven't gotten one after 4 weeks?Do I accept an offer from a company that I am not likely to join?New job hasn't confirmed starting date and I want to give current employer as much notice as possibleHow should I address my manager in my resignation letter?HR delayed background verification, now jobless as resignedNo email communication after accepting a formal written offer. How should I phrase the call?What should I do if after receiving a verbal offer letter I am informed that my written job offer is put on hold due to some internal issues?Should I inform the current employer that I am about to resign within 1-2 weeks since I have signed the offer letter and waiting for visa?What company will do, if I send their offer letter to another company