FAQ - Revision history

Nathanrwells: /* Common Storage For Projects */

2025-06-26T13:48:52Z

Common Storage For Projects

← Older revision		Revision as of 08:48, 26 June 2025
Line 209:		Line 209:
	Sometimes it is useful for groups of people to have a common storage area.		Sometimes it is useful for groups of people to have a common storage area.

	If you do not have a project, send a request ~~via email~~ to ~~beocathelp@ksu.edu or contact~~ Beocat staff through a [https://support.ksu.edu/TDClient/30/Portal/Requests/ServiceDet?ID=44 TDX Ticket]. Note that these projects are generally reserved for tenure-track faculty and with a single project per eID.		If you do not have a project, send a request to Beocat staff through a [https://support.ksu.edu/TDClient/30/Portal/Requests/ServiceDet?ID=44 TDX Ticket]. Note that these projects are generally reserved for tenure-track faculty and with a single project per eID.

	If you already have a project you can do the following:		If you already have a project you can do the following:

Nathanrwells: /* Common Storage For Projects */

2025-06-23T20:19:58Z

Common Storage For Projects

← Older revision		Revision as of 15:19, 23 June 2025
Line 209:		Line 209:
	Sometimes it is useful for groups of people to have a common storage area.		Sometimes it is useful for groups of people to have a common storage area.

	If you do not have a project, send a request via email to ~~beocat~~@cs.ksu.edu. Note that these projects are generally reserved for tenure-track faculty and with a single project per eID.		If you do not have a project, send a request via email to beocathelp@ksu.edu or contact Beocat staff through a [https://support.ksu.edu/TDClient/30/Portal/Requests/ServiceDet?ID=44 TDX Ticket]. Note that these projects are generally reserved for tenure-track faculty and with a single project per eID.

	If you already have a project you can do the following:		If you already have a project you can do the following:

Mozes: /* Automating Duo Method */

2024-01-26T23:56:44Z

Automating Duo Method

← Older revision		Revision as of 18:56, 26 January 2024
Line 45:		Line 45:
	You would need to configure your connection client to send an ''Environment'' variable called <tt>DUO_PASSCODE</tt>. Its value could be the currently valid passcode from Duo, <tt>push</tt> or it could be set to <tt>phone</tt>. <tt>push</tt> will push the prompt to your smart device. <tt>phone</tt> will have duo call your phone number to approve.		You would need to configure your connection client to send an ''Environment'' variable called <tt>DUO_PASSCODE</tt>. Its value could be the currently valid passcode from Duo, <tt>push</tt> or it could be set to <tt>phone</tt>. <tt>push</tt> will push the prompt to your smart device. <tt>phone</tt> will have duo call your phone number to approve.

			===== OpenSSH =====
	With OpenSSH (Linux or Mac command-line), to automatically set the Duo method to "push", use the command		With OpenSSH (Linux or Mac command-line), to automatically set the Duo method to "push", use the command
	<syntaxhighlight lang="bash">DUO_PASSCODE=push ssh -o SendEnv=DUO_PASSCODE headnode.beocat.ksu.edu</syntaxhighlight>		<syntaxhighlight lang="bash">DUO_PASSCODE=push ssh -o SendEnv=DUO_PASSCODE headnode.beocat.ksu.edu</syntaxhighlight>

			If you would like to put this in your ~/.ssh/config file, it will send the environment variable whenever it is set to Beocat upon connection:
			Host headnode.beocat.ksu.edu
			HostName headnode.beocat.ksu.edu
			User YOUR_EID_GOES_HERE
			SendEnv DUO_PASSCODE

			From there you would simply do the following:
			<syntaxhighlight lang=bash>
			export DUO_PASSCODE=push
			ssh headnode.beocat.ksu.edu
			</syntaxhighlight>

			===== PuTTY =====
	In PuTTY to automatically set the Duo method to "push", expand "Connection" (if it isn't already), then click "Data". Under Environment variables, enter '''<tt>DUO_PASSCODE</tt>''' beside ''Variable'' and '''<tt>push</tt>''' beside ''Value''. Click the "Add" button and it will show up underneath. Be sure to go back to "Session" to save this change for PuTTY to remember this change.		In PuTTY to automatically set the Duo method to "push", expand "Connection" (if it isn't already), then click "Data". Under Environment variables, enter '''<tt>DUO_PASSCODE</tt>''' beside ''Variable'' and '''<tt>push</tt>''' beside ''Value''. Click the "Add" button and it will show up underneath. Be sure to go back to "Session" to save this change for PuTTY to remember this change.

			===== MobaXTerm =====
	There doesn't seem to be a way to send an environment variable in MobaXTerm, so you won't be able to set DUO_PASSCODE to an actual valid temporary key. To get MobaXterm to push automatically, you can edit your SSH session and on the "Advanced SSH Settings" tab, change the "Execute command" to <syntaxhighlight lang="bash">DUO_PASSCODE=push bash</syntaxhighlight>		There doesn't seem to be a way to send an environment variable in MobaXTerm, so you won't be able to set DUO_PASSCODE to an actual valid temporary key. To get MobaXterm to push automatically, you can edit your SSH session and on the "Advanced SSH Settings" tab, change the "Execute command" to <syntaxhighlight lang="bash">DUO_PASSCODE=push bash</syntaxhighlight>

Mozes: /* Help! when I use sbatch I get an error about line breaks */

2023-10-12T00:05:27Z

Help! when I use sbatch I get an error about line breaks

@@ Line 177: / Line 177: @@
 * Visual Studio Code -- “Text Editor” > “Files” > “Eol”
 * Notepad++ -- "Edit" > "EOL Conversion"
 == Common Storage For Projects ==

Mozes: /* How are the filesystems on Beocat set up? */

2023-08-25T23:22:01Z

How are the filesystems on Beocat set up?

← Older revision		Revision as of 18:22, 25 August 2023
Line 91:		Line 91:
	! Mountpoint !! Local / Shared !! Size !! Filesystem !! Advice		! Mountpoint !! Local / Shared !! Size !! Filesystem !! Advice
	\|-		\|-
	\| /bulk \|\| Shared \|\| 3.1PB shared with /homes ~~and /scratch~~ \|\| cephfs \|\| Slower than /homes; costs $45/TB/year		\| /bulk \|\| Shared \|\| 3.1PB shared with /homes \|\| cephfs \|\| Slower than /homes; costs $45/TB/year
	\|-		\|-
	\| /homes \|\| Shared \|\| 3.1PB shared with /bulk ~~and /scratch~~ \|\| cephfs \|\| Good enough for most jobs; limited to 1TB per home directory		\| /homes \|\| Shared \|\| 3.1PB shared with /bulk \|\| cephfs \|\| Good enough for most jobs; limited to 1TB per home directory
	\|-		\|-
	\| /fastscratch \|\| Shared \|\| 280TB \|\| nfs on top of ZFS \|\| Faster than /homes or /bulk, built with all NVME disks; files not used in 30 days are automatically culled.		\| /fastscratch \|\| Shared \|\| 280TB \|\| nfs on top of ZFS \|\| Faster than /homes or /bulk, built with all NVME disks; files not used in 30 days are automatically culled.

Mozes: /* How are the filesystems on Beocat set up? */

2023-08-25T23:21:40Z

How are the filesystems on Beocat set up?

← Older revision		Revision as of 18:21, 25 August 2023
Line 95:		Line 95:
	\| /homes \|\| Shared \|\| 3.1PB shared with /bulk and /scratch \|\| cephfs \|\| Good enough for most jobs; limited to 1TB per home directory		\| /homes \|\| Shared \|\| 3.1PB shared with /bulk and /scratch \|\| cephfs \|\| Good enough for most jobs; limited to 1TB per home directory
	\|-		\|-
	~~\| /scratch \|\| Shared \|\| 3.1PB shared with /bulk and /homes \|\| cephfs \|\| Fast shared tmp space; files not used in 30 days are automatically culled~~		\| /fastscratch \|\| Shared \|\| 280TB \|\| nfs on top of ZFS \|\| Faster than /homes or /bulk, built with all NVME disks; files not used in 30 days are automatically culled.
	\|-
	\| /fastscratch \|\| Shared \|\| 280TB \|\| nfs on top of ZFS \|\| Faster than /~~scratch~~, built with all NVME disks; files not used in 30 days are automatically culled.
	\|-		\|-
	\| /tmp \|\| Local \|\| >100GB (varies per node) \|\| XFS \|\| Good for I/O intensive jobs. Unique per job, culled with the job finishes.		\| /tmp \|\| Local \|\| >100GB (varies per node) \|\| XFS \|\| Good for I/O intensive jobs. Unique per job, culled with the job finishes.

Mozes: /* Common Storage For Projects */

2023-08-16T17:23:44Z

Common Storage For Projects

← Older revision		Revision as of 12:23, 16 August 2023
Line 195:		Line 195:
	** <tt>setfacl -m g:$group_name:rX -R $directory</tt>		** <tt>setfacl -m g:$group_name:rX -R $directory</tt>

	This will give people in your group the ability to read files in the 'share' directory. If you also want them to be able to write or modify files in that directory then use change the ':rX' to ':rwX' instead. e.g. 'setfacl -d -m g:$group_name:rwX -R $directory' for both setfacl commands. As with other permissions, the individuals will need access through every level of the directory hierarchy. [[LinuxBasics#Access_Control_Lists It may be best to review our more in-depth topic on Access Control Lists.]]		This will give people in your group the ability to read files in the 'share' directory. If you also want them to be able to write or modify files in that directory then use change the ':rX' to ':rwX' instead. e.g. 'setfacl -d -m g:$group_name:rwX -R $directory' for both setfacl commands. As with other permissions, the individuals will need access through every level of the directory hierarchy. [[LinuxBasics#Access_Control_Lists\|It may be best to review our more in-depth topic on Access Control Lists.]]

	== How do I get more help? ==		== How do I get more help? ==

Mozes: /* Common Storage For Projects */

2023-08-16T17:23:26Z

Common Storage For Projects

← Older revision		Revision as of 12:23, 16 August 2023
Line 195:		Line 195:
	** <tt>setfacl -m g:$group_name:rX -R $directory</tt>		** <tt>setfacl -m g:$group_name:rX -R $directory</tt>

	This will give people in your group the ability to read files in the 'share' directory. If you also want them to be able to write or modify files in that directory then use change the ':rX' to ':rwX' instead. e.g. 'setfacl -d -m g:$group_name:rwX -R $directory' for both setfacl commands.		This will give people in your group the ability to read files in the 'share' directory. If you also want them to be able to write or modify files in that directory then use change the ':rX' to ':rwX' instead. e.g. 'setfacl -d -m g:$group_name:rwX -R $directory' for both setfacl commands. As with other permissions, the individuals will need access through every level of the directory hierarchy. [[LinuxBasics#Access_Control_Lists It may be best to review our more in-depth topic on Access Control Lists.]]

	== How do I get more help? ==		== How do I get more help? ==

Mozes: /* Common issues */

2023-08-02T16:38:15Z

Common issues

← Older revision		Revision as of 11:38, 2 August 2023
Line 53:		Line 53:

	==== Common issues ====		==== Common issues ====
			; Duo Pushes sometimes don't show up in a timely manner.
			: If you open the Duo MFA application on your smart device when you're expecting an authentication challenge, the prompts seem to show up faster.
	; MobaXTerm has excessive prompts for managing files.		; MobaXTerm has excessive prompts for managing files.
	: MobaXTerm has a sidebar browser for managing your files. Unfortunately, that sidebar browser initiates another SSH connection for every file transfer, which triggers a Duo push that you need to approve. MobaXTerm's dedicated SFTP Session doesn't have this same issue, it initiates a connection, keeps it open and re-uses it as needed, so you will have much fewer Duo approvals to respond to. If you choose to use the dedicated SFTP Session, you might consider disabling the sidebar file browser. "Advanced SSH settings" -> "SSH-browser type" -> "None"		: MobaXTerm has a sidebar browser for managing your files. Unfortunately, that sidebar browser initiates another SSH connection for every file transfer, which triggers a Duo push that you need to approve. MobaXTerm's dedicated SFTP Session doesn't have this same issue, it initiates a connection, keeps it open and re-uses it as needed, so you will have much fewer Duo approvals to respond to. If you choose to use the dedicated SFTP Session, you might consider disabling the sidebar file browser. "Advanced SSH settings" -> "SSH-browser type" -> "None"
	~~; Duo Pushes sometimes don't show up in a timely manner.~~
	~~: If you open the Duo MFA application on your smart device when you're expecting an authentication challenge, the prompts seem to show up faster.~~
	; WinSCP has auto-reconnect enabled by default.		; WinSCP has auto-reconnect enabled by default.
	: Auto-reconnect is a useful function when actively transferring files, but if you have an idle session and the connection drops it will reconnect, sending you a Duo MFA prompt. If you don't approve it soon enough, WinSCP will attempt it again. Miss enough prompts and Duo will lock your account. It may be best to disable [https://winscp.net/eng/docs/ui_pref_resume reconnections during idle periods] if you do not wish be locked out of all services at K-State using Duo.		: Auto-reconnect is a useful function when actively transferring files, but if you have an idle session and the connection drops it will reconnect, sending you a Duo MFA prompt. If you don't approve it soon enough, WinSCP will attempt it again. Miss enough prompts and Duo will lock your account. It may be best to disable [https://winscp.net/eng/docs/ui_pref_resume reconnections during idle periods] if you do not wish be locked out of all services at K-State using Duo.

Mozes: /* Common issues */

2023-08-02T16:37:51Z

Common issues

← Older revision		Revision as of 11:37, 2 August 2023
Line 61:		Line 61:
	; FileZilla has auto-reconnect enabled by default.		; FileZilla has auto-reconnect enabled by default.
	: Auto-reconnect is a useful function when actively transferring files, but if you have an idle session and the connection drops it will reconnect, sending you a Duo MFA prompt. If you don't approve it soon enough, FileZilla will attempt it again. Miss enough prompts and Duo will lock your account. It may be best to disable timeouts and/or connection retries under the <tt>Edit -> Settings -> Connection</tt> menu if you do not wish to be locked out of all services at K-State using Duo.		: Auto-reconnect is a useful function when actively transferring files, but if you have an idle session and the connection drops it will reconnect, sending you a Duo MFA prompt. If you don't approve it soon enough, FileZilla will attempt it again. Miss enough prompts and Duo will lock your account. It may be best to disable timeouts and/or connection retries under the <tt>Edit -> Settings -> Connection</tt> menu if you do not wish to be locked out of all services at K-State using Duo.
			; FileZilla has excessive prompts for managing files.
			: Filezilla opens one connection for browsing the system. Transferring files opens 1-4 additional connections when the transfers start. Once they finish, those connections disconnect. If you start additional transfers, new connections will be opened. Every one of those connections must be approved through Duo MFA on your smart device. You can adjust the number of connections that FileZilla opens for transfers if you like. <tt>File -> Site Manager -> (choose the site you're changing) -> Transfer Settings -> Limit number of simultaneous connections</tt>.
			: Another option is to disable processing the transfer queue, add the things to it you want to transfer and then re-enable the transfer queue. Then at least it will re-use the connections until the queue is empty.

	== How do I compile my programs? ==		== How do I compile my programs? ==