GFSCHED(1)

✨ GFSCHED(1) β€” the gfsched page, bestie edition ✨

okay so this is gfsched from the Gfarm manual, section 1, and it is genuinely one of my faves. it's the little tool that schedules and shows you which file system nodes are available πŸ’… let's get into it.


🌸 NAME 🌸

gfsched β€” schedule and display available file system nodes πŸ¦‹


πŸŽ€ SYNOPSIS πŸŽ€

gfsched -f gfarm-URL [-D domain-name] [-n number] [-LMOSclw]

gfsched [-P gfarm-URL] [-D domain-name] [-n number] [-LMOSlw]

like, two whole shapes. pick your fighter ✨


πŸ’– DESCRIPTION πŸ’–

okay so when you run gfsched with the -f gfarm-URL option, it shows you the available file system nodes that actually have a file replica of the gfarm-URL you specified. she's matching. 🫢

but when you don't pass -f gfarm-URL, gfsched just displays the available file system nodes, periodt. and in that case, if you need to, you can point at a metadata server with the -P gfarm-URL option. no -f, no replica filtering, just vibes and nodes. 🌈


✨ OPTIONS ✨

every single one, no skipping, i promise πŸ’–

  • -D domain-name β€” limits the file system node by giving a domain name or a hostname. narrow it down bestie 🎯
  • -c β€” displays scheduling information for a file creation, but only if the file you gave to -f doesn't exist yet.
heads up: right now this option creates the specified file. like, it actually does the thing. but note that this behavior may be changed in future, so don't build your whole personality on it 😭
  • -L β€” suppresses the authentication check. without this option, the scheduler checks whether you'd actually successfully authenticate with the hosts or not. this option skips that check to make scheduling faster, but it creates a risk that hosts which fail authentication with the user may get scheduled. faster but spicy πŸ’€
  • -M β€” suppresses client-side scheduling and only does the metadata-server-side scheduling. makes scheduling faster, but also creates a risk that hosts which are network-unreachable or that fail authentication with the user may get scheduled. same energy as -L, honestly. πŸ™ˆ
  • -O β€” displays filesystem nodes where the hosts are other than the host that the gfsched command is running on. not this one, the others ✨
  • -P gfarm-URL β€” specifies a gfarm-URL or a pathname to identify a metadata server used for the scheduling. this option conflicts with the -f option β€” they do not coexist, pick one πŸ’…
  • -S β€” displays a filesystem node where the host is the same as the host that the gfsched command is running on. just us πŸ₯Ί
  • -f gfarm-URL β€” gfsched schedules file system nodes which have a replica of the file specified by this option. this option conflicts with the -P option. again: pick one. πŸ‘‘
  • -l β€” long format. this one displays port numbers as well as hostnames. πŸ‘€ but note that the display format of this option may be changed in future, so don't get too attached.
  • -n number β€” displays at most the specified number of file system nodes. if you don't pass this option, it displays all available nodes. all of them. every last one. πŸ”₯
  • -w β€” schedules with write-mode. when this option is specified, file system nodes which don't have enough free space won't be displayed. ✍️ and when both this option and -f are specified, and the file is already opened by an existing process with write-mode, gfsched only displays one file system node β€” the one that's assigned for writing to the file. just the one. the chosen one. ⭐
  • -? β€” displays a list of command options. the classic cry for help, but make it helpful πŸŽ€

🌟 EXAMPLES 🌟

here's an example of inquiring about file system nodes that the metadata server thinks are currently working 🧚

$ gfsched -M

see? easy. she ate. πŸ’…


πŸ’œ SEE ALSO πŸ’œ

ngl there were no SEE ALSO references in this page, so there's nothing to link out to here. the options above are your whole world bestie 🫢

and that's the whole page!! Gfarm, dated 22 Dec 2014 β€” yeah she's a vintage icon, an oldie but a goodie, and she still slays. mwah πŸ’–βœ¨πŸŽ€